Posted by raylopez99 on 04/01/07 11:22

On Apr 1, 3:22 am, Erland Sommarskog <esq...@sommarskog.se> wrote:

>
> Note by the way that this is all SQL commands. While point-and-click
> GUIs for table design can make you work faster if you are unexperienced,
> learning the SQL commands is absolutely essential if you plan for a
> professional career in SQL programming. Once you know the commands well,
> you can use GUI tools if you find that more convenient. But all the
> tools do is to generate the commands like the above, and without knowledge
> and understanding of that, you are pretty clueless when things go wrong.
>
> --
> Erland Sommarskog, SQL Server MVP, esq...@sommarskog.se
>
> Books Online for SQL Server 2005 athttp://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books...
> Books Online for SQL Server 2000 athttp://www.microsoft.com/sql/prodinfo/previousversions/books.mspx

Thanks Erland--I have bookmarked your example for future reference,
after I read some SQL books I ordered. Right now I'm trying to just
learn how the SQL editor and IDE work. For some strange reason I was
able to "save" the same example while as Administrator rather than
PowerUser, but I think it's just a coincidence--I must have inserted a
wrong word or some wrong semantics in the PowerUser version, which is
kept in its own seperate database. Permissions seems to be a big deal
with modern SQL databases BTW--eventually I hope to figure out how to
manipulate permissions on the fly with commands, as you seemed to show
in another thread.

Seems like SQL is like a macro language that is "top-down" procedural
and definitely not object oriented of course.

Now onto the next topic in my SQL GUI paint-by-numbers book:
connected vs disconnected ADO.NET (I program for fun, not
professionally).

RL

[Back to original message]