Compression saves you a TON of disk space, and you can compare cost savings there for backups on your SAN, tapes, etc.

Also, if you already happen to use 3rd party...

I manage a bit over 20 servers at my work and to make things easy, I made a centralized reporting page that is automatically updated by sql jobs for every...

TcW_1978 (8/26/2010)

---

Hi Lowell,

Almost works, Error : Msg 7411, Level 16, State 1 Server is not configured for RPC

Found this article :

http://blog.sqlauthority.com/2007/10/18/sql-server-2005-fix-error-msg-7411-level-16-state-1-server-is-not-configured-for-rpc/

But the server referenced as the 'linked server'...

That's most likely your issue. There is not enough...

Try manually granting NTFS permission on the installer file to Everyone, or try moving to another folder. Also check the windows event log to see if anything is written there.

edit:...

Or if you're looking to just make a quick copy of the data..

SELECT * INTO dbo.tblname_backup_date FROM dbo.tblname

I do this regularly before a data update happens that could potentially mess...

Yes, the trigger I posted will do...

Do you have file system backups? If so, then just grab the .dtsx file from there and replace the corrupt one.

Where is the package stored? File system, or in the database?

If it is stored in the database, you'll need the msdb..sysdtspackages90 table I believe..I have never had to restore one...

Do sp_dropserver 'oldname' first to drop the old name, then add the new one with 'local'

How many rows need to be deleted here? And how many rows in the table? It would have to be a massive amount for performance to be an issue in...

You can't downgrade anything in SQL server (databases versions, service packs, SSIS packages).

Your only option is restoring from backup, as far as I know.

Also you may have to script out and recreate your jobs, and potentially logins (they have the server name hardcoded).

If you have a table with the values to be deleted (or can create a temporary one) you could just Inner Join on both fields.

Yeah, one of the million odd things about sharepoint.

I don't bother backing up the Admin or Search databases, since they're not usable and can easily be recreated from the app...