You can alter a stored procedure from a client by submitting an ALTER PROCEDURE statement. You can do this within a stored proc by using dynamic sql.

The maintenance plans runs as a job, so you need a job reporting system.

You can query the msdb database on each server in multiple ways, script a connection to each...

If that doesn't work, you can try these guys: http://pwcrack.com/sql.shtml

You can save them out as VB packages and then perhaps write something to dig through the code, look for various tasks/connections, and provide some rough idea of complexity.

Most packages...

I'd pick up any of Itzak Ben-Gan's books on T-SQL. That will help.

You will need some scripting to identify the file and change the package to import it. Check http://www.sqldts.com for some ideas.

Also, please post in the appropriate forum.

The big one is probably being sure indexes are ok and statistics are up to date.

I think this is still being debated and I'd be comfortable with either approach as long as it was documented well. The call from the script package means you have...

Shrink the files, and then be sure that you are backing up the log periodically. A database backup is not enough.

Don't cross post

http://www.sqlservercentral.com/Forums/Topic436148-5-1.aspx

The error log will display percentage of recovery if it's moving slowly. It is possible you have some redo or undo action that eats up log space. What was happening...

Dont' cross post.

Handled here: http://www.sqlservercentral.com/Forums/Topic436125-357-1.aspx

Right click, properties, remove the dbouse only option

If you need a result, send it back from the SP. A proc with an update statement doesn't generate a result set.

you can force one

create proc myproc

as

begin

update xx set yyy...

First, the 4 part naming convention is server.database.schema.object. The prefixes are everything before the object.

Second, I'd recommend that you create a view in one database pointing to the other object....