Posted by Erland Sommarskog on 04/01/07 15:16

raylopez99 (raylopez99@yahoo.com) writes:
> 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

Probably because the first time the procedure wasn't there, so CREATE was
the right thing. The second time round, ALTER is the right thing.

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

SQL is hardly a macro language, but it's true that neither is it object-
oriented. And it is different from traditional programming. In a traditional
programming when you want to operate on many objects of the same time you
run a loop. In SQL you operate on all rows at once, and the optimizer out
which is the best way to do this.


--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx

• Next in forum: Re: SQL Datatypes
• Prev in forum: Re: I have a database on a network drive that I use for archiving purposes, but when the server is rebooted the database becomes suspect.
• Thread view: Re: The old inability to toggle/change/switch between ALTER PROCEDURE <---> CREATE PROCEDURE bug (or is it a feature?)

[Reply to this message]