Restoring a database from a backup restores everything in the database, including users and permissions.

If you need to copy only permissions, you'll have to script them. There are several...

Since you can only use built-in notification for one of those, I would put EXEC xp_sendmail in a couple of job steps for the other two situations. For example,...

Silverfox (9/14/2009)

You...

My preferred method is to script the table schema in the source database and use the Import/Export Wizard to move the data. I either run the script in a...

Any connection in the package that uses Windows authentication will use the credentials of the login executing the package. When the package is executed in a job, the SQL...

Someone has filed a bug report about this http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=371669.

Apparently, Discover depedency doesn't work for jobs. The workaround is to go to Tools -> Options -> Scripting and...

I think you're getting that message because the login wasn't renamed in Windows i.e. both logins exist. I think your only option is to add domain\prod_sqluser as a login...

Well, there was no DTS package option in SQL 2000 jobs either. You run DTS packages in CmdExec steps just like in SQL 2000.

Create a new SQL Agent job...

All you're doing by answering "yes" is creating the system tables and stored procedures needed to create and maintain diagrams, so you shouldn't expect any harm.

You could script the packages to vb files and edit them to search for connections. There's at least one script in SSC's script section that will script all the...

I'm pretty sure you can't do what you want using the SSIS roles. You'd have better luck storing the packages in file system folders and restricting access to those.

Because maintenance plans in SQL 2005 are saved as SSIS packages, you can't script the plans. You can, however, save the packages as files to make them portable.

The statement fails because you're only selecting two columns from t_line. The select list of the subquery must match the column list of the INSERT. The same rule...

A developer doesn't need any SQL Server permissions to create a package because that's done outside of SQL Server in Business Intelligence Development Studio (BIDS). BIDS should be installed...

Describe what you see when you try to create a diagram for the databases it doesn't work. Do you get a message?