In Database We Trust

Question

In Database We Trust

Viewing 6 posts - 16 through 20 (of 20 total)

You must be logged in to reply to this topic. Login to reply

notarian@gmail.com SSCommitted Points: 1950 More actions · Answer 1

Well, I am dealing with a vendor that has a table named [NULL], numerous columns named [NULL], and I was completely surprised they didn't just name the database [NULL].

Security by obscurity? This reminds me of the DOS days when at my high school people would hide games inside folders with names of 12 spaces or special characters nested 12 deep.

Hany Helmy SSChampion Points: 13921 More actions · Answer 2

SQLRNNR (2/19/2014)
Definitely an interesting question.
It makes you think about the difference between a reserved keyword and just a keyword.

+ 1

Thanks & Best Regards,
Hany Helmy
SQL Server Database Consultant

Hany Helmy SSChampion Points: 13921 More actions · Answer 3

SQLRNNR (2/20/2014)
Well, I am dealing with a vendor that has a table named [NULL], numerous columns named [NULL], and I was completely surprised they didn't just name the database [NULL].

😀

Thanks & Best Regards,
Hany Helmy
SQL Server Database Consultant

PChiragS SSCarpal Tunnel Points: 4965 More actions · Answer 4

PChiragS

SSCarpal Tunnel

Points: 4965

February 24, 2014 at 9:16 am

#1691611

nice question..

thanks for sharing Andy.

sqlnaive SSCoach Points: 17437 More actions · Answer 5

SQLRNNR (2/19/2014)
Definitely an interesting question.
It makes you think about the difference between a reserved keyword and just a keyword.

+1 🙂

Anoo S Pillai Mr or Mrs. 500 Points: 547 More actions · Answer 6

From the Answer - "The database does get set to trustworthy even though the database is read only at that point. It may not be obvious, but the trustworthy setting is stored in master and not in the database " - Nice catch Andy. Thanks for sharing.