You can also use tools like ERWIN, EMBARCARDEO and datacompare to just generate the scripts of your tables for you. but the best is to use the SSMS for that.

Your sql server will be running in local system account. change that to domain account so that the server will be able to mutally authenticate itself.

Yes wondering out where is it specified that you should not use sa as a database owner. The link of that will let us know what the bad practice it...

Generally i go with the dbo schema. so that i can get hold on things easily and know what is happening in my server and moreover implementation in the production...

1. update stats

2. execute DBCC UPDATEUSAGE

3. if any repopulate full text catalogs

One thing that i can think quickly for such a huge number of databases is using Doubletake for replication of the databases at the file level and then using a...

Use your agent login itself to be used for the Maintenance plans.

You can backup the database to a TAPE or the DVD and then ship it to the destination.

Bring the database offline. And when you need it back bring it online and hence use it.

You can script all your jobs in a moment using the script jobs task that is available.

Can't understand this. You have a merge replication setup and in one of your server the processes are numbering...

You can install SP2 for SQL 2005 so that you would have the lastest installed.

You can use the builtin alerts available with SQL Server for your req. But still if you want to handle via a TSQL then you would need to code with...

When you mean dynamic how do you get the server name to add to the connection string. I know the you are using windows credentials and there is no need...

Use the service account as the connection property string in your sql server replication rather than using sa account as that account gets its password changed depending on the business...