Ahahaha, try to write a sp and mistype the name of a table...
Is a complete nightmare!!! You can only discover this when the
sp is out, SQL Server don't ever warns you!!!
And other: if, in a SQL Server machine, someone invades one of the
databases and becames the owner of that database (even a non-important,
testing or a unrelated db) it is a one easy pass of became the owner of
the server!!!!!!!!!!! Maybe (i'm not 100% sure) even with full access the
server's filesystems through the MSSQL.
Bah, what a crappy DB server... And this is NOT a lame blame, I work
with MSSQL 2000 and discovered this!!!!!

[]s Fabricio

On Thu, 11 Oct 2001 22:17:36 +1000, Helen Borrie wrote:

>At 01:41 PM 11-10-01 +0200, you wrote:
>>At 12:24 2001-10-11 +0100, you wrote:
>>
>>
>> > > This is one of the main reasons why we will probably swutch to another
>> > > database, e.g. SQL Server, etc. It will be a great pity, because I really
>> > > like IB and the projects I have done on it run beautifully...
>> >
>> >1. I don't think SQL Server will allow you to do metadata changes on fly,
>> >but please correct me if I am wrong. Certainly Sybase didn't.
>>
>>I am not 100% sure myself, but my wife works with it and says it can. Still
>>need to investigate though...
>
>Sure, SQL Server stored procedures are COOL. As long as they syntax-check OK, they get written out in interpreter
code and the next user can invoke them straight away. They get precompiled "just-in-time" and any data integrity or
validation errors and logic bugs will present themselves to the user for "in-line QA".
>
>No thanks.
>
>Helen
>
>All for Open and Open for All
>InterBase Developer Initiative · http://www.interbase2000.org
>_______________________________________________________
>
>
>To unsubscribe from this group, send an email to:
>ib-support-unsubscribe@egroups.com
>
>
>
>Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>


[]s Fabricio
Systems Developer