Beyond SQL

Dear gurus,
Which are the most difficult tasks for a guru? Which would be the most
complex task concerning RDBMS?
I am not talking about administrative tasks, common routines, left join
issues, nested cursors, etc, but amazing milestones, strange jobs or
nightmares using the maximum capabilities of SQL engine.
Thanks in advance and regards,,How do you define "guru"?
Adam Machanic
SQL Server MVP
http://www.datamanipulation.net
--
"Enric" <Enric@.discussions.microsoft.com> wrote in message
news:9A450896-F654-43D4-9755-1C4A5C0580F2@.microsoft.com...
> Dear gurus,
> Which are the most difficult tasks for a guru? Which would be the most
> complex task concerning RDBMS?
> I am not talking about administrative tasks, common routines, left join
> issues, nested cursors, etc, but amazing milestones, strange jobs or
> nightmares using the maximum capabilities of SQL engine.
> Thanks in advance and regards,,|||"Enric" <Enric@.discussions.microsoft.com> wrote in message
news:9A450896-F654-43D4-9755-1C4A5C0580F2@.microsoft.com...
> Dear gurus,
> Which are the most difficult tasks for a guru? Which would be the most
> complex task concerning RDBMS?
> I am not talking about administrative tasks, common routines, left join
> issues, nested cursors, etc, but amazing milestones, strange jobs or
> nightmares using the maximum capabilities of SQL engine.
> Thanks in advance and regards,,
The biggest hurdle I have seen lately is moving from a small to medium size
database architecture and schema and then designing and developing and
migrating that solution to a VLDB environment. There are a lot of potential
gotchas and mistakes that are made.
It is one thing to design speed and intelligence into a system that works
with 100 million rows and something else entirely when you are dealing with
billions of rows.
Just my .02
Rick Sawtell|||Trying to avoid the throngs of female fans while on public outings;
especially if they show up at user group meetings and sit on the front row
just drooling while you're trying to give a presentation. Then there are the
weird gs who walk up to the table (while at a restraunt with the wife and
kids) and shove some 20 page sample of crap SQL under your nose expecting
you to somehow shed some light on their problem between bites of veal
parmesan. Once you reach a certain level of popularity, it can be a real
problem.
"Enric" <Enric@.discussions.microsoft.com> wrote in message
news:9A450896-F654-43D4-9755-1C4A5C0580F2@.microsoft.com...
> Dear gurus,
> Which are the most difficult tasks for a guru? Which would be the most
> complex task concerning RDBMS?
> I am not talking about administrative tasks, common routines, left join
> issues, nested cursors, etc, but amazing milestones, strange jobs or
> nightmares using the maximum capabilities of SQL engine.
> Thanks in advance and regards,,|||I wouldn't call myself a guru, but what the hell.
For me, understanding the business is always the most critical and most
difficult part of my job. Until I understand how the business's data
IS - that is, what it is, what is an attribute of what, how it relates
within itself and how it flows - I am effectively spinning my wheels.
Free advice, freely given - worth what you pay for it.
Payson
> "Enric" <Enric@.discussions.microsoft.com> wrote in message
> news:9A450896-F654-43D4-9755-1C4A5C0580F2@.microsoft.com...|||LOL. Not to mention the paparizzi - who can script with all those camera
flashes?|||That's why we have body guards and ride around in limos with tented windows.
;-)
"Scott Morris" <bogus@.bogus.com> wrote in message
news:%23ffSONzoFHA.3120@.TK2MSFTNGP09.phx.gbl...
> LOL. Not to mention the paparizzi - who can script with all those camera
> flashes?
>