Just as a quick note, though it's likely not going to come up in the test:
Storing tables, stored procedures (sprocs), views, and so on in 'master' is generally considered incorrect. You want to create a database that you then store these things in. 'master' is where all the important bits that drive SQL Server live, and stepping on them -- as you all too easily can with sa access -- is, uh, bad form, to say the least.
User functions are permissible in master, generally, but it's still better to slap them into their own database too.
Basically, it's like storing all your documents in, say, c:windowssystem32 (for a Windows box). Can you? Sure. Will it break anything? Probably not. Does it increase your risk of ham-fingering something and blowing stuff up? Hell yes.
--sofaspud
--"Listening to your kid is the audio equivalent of a Salvador Dali painting, Spud." --OpMegs
Storing tables, stored procedures (sprocs), views, and so on in 'master' is generally considered incorrect. You want to create a database that you then store these things in. 'master' is where all the important bits that drive SQL Server live, and stepping on them -- as you all too easily can with sa access -- is, uh, bad form, to say the least.
User functions are permissible in master, generally, but it's still better to slap them into their own database too.
Basically, it's like storing all your documents in, say, c:windowssystem32 (for a Windows box). Can you? Sure. Will it break anything? Probably not. Does it increase your risk of ham-fingering something and blowing stuff up? Hell yes.
--sofaspud
--"Listening to your kid is the audio equivalent of a Salvador Dali painting, Spud." --OpMegs