You inherited a brand new SQL server, one of the first questions you ask is of course where is the source control for this servers I want to see all the procedures and jobs. The answer might be that they use daily backups as source control or just don't do any source control at all.

If you want all jobs into one file then you don't need to use SMO since there is an easier solution, take a look here: Scripting all jobs on SQL Server 2005/2008 into one file

If yo...

There seems to be a little bit of confusion on how to script out the database. The correct answer is of course: just run all the scripts you have in source control :-)

So for those who do not use/have source control I will show you how to do it

Logically you would think that this would be the way: Right click on the database --> Script Database As --> CREATE To and then pick your choice. See also image below

What that will do is just create the database...

This question came up recently so I decided to blog about it

If you have your stored procedures in source control and you want to see if they are the same as the one on the server, all you need to do is script out the procs and do a diff right?

Let's see what happens, create this proc