As previously said, if you system is a highly transactional system, shrinking it will have no affect on filesize and in return might have significant performance impact as there might...

You havent mentioned the complete details:

What is the Sql Server Edition and SP info (hope you are not running Express or MSDE...

What is the OS (version and Edition)

How much...

First Define your Migration Strategy:

is it SQL 2000 to 2005 or SQL 2000 to 2008 or 2005 to 2008

Then go for it:

Anyways.. use the SQL Server upgrade Advisor Tool.

I would...

Did you setup the master/Target servers.. under SQl server Agent.

Goto-> SQL server Agent-> right click and select Multiserver Administration->seect make this the master or target.

I havent played around with this...

Regarding your script:

Try to change the Database contect to the database you are trying to run the script in.

use then run your cursor.

Because the sys.indexes might be relating...

Following up on my previous thread:

you can restrict the query by database_id = with out the sp_msforeachdb query will look like this:

select 'ALTER INDEX '+ss.name+ ' ON '+...

Klnsuddu,

Here is your explanation and the link:

If a shrink operation tries to truncate a file while a backup is running, the shrink stops without truncating the file, however data...

Try to Run the Backup Log at a seprate time than DBCC CHECKDB. This wil help minimize performance issues if any. but of your Database and log sizes are BIG,...

Are there 2 or more jobs running at the same time, which might affect the same database, like while the backup is running the transaction log can also kick in...

SET TRANSACTION ISOLATION LEVEL read committed

see if this solves your purpose:

sp_msforeachdb @command1 = 'USE [?]; select ''ALTER INDEX ''+ss.name+ '' ON ''+ object_name(si.object_id,si.database_id)+'' REBUILD ;'', db_name(si.database_id),

ss.name,si.avg_fragmentation_in_percent

from sys.dm_db_index_physical_stats (DB_id(),NULL,NULL,NULL,NULL) si

join sys.indexes ss on si.object_id=ss.object_id ...

Try this and check the results to look for duplicate names or otherwise... any altered procedures...etc

sp_msforeachdb @command1 = ' USE [?]; select db_name() as dbname, specific_catalog,routine_name,created,last_altered from information_Schema.routines

Where last_altered >=...

Did you check the permissions to the Folder where the SSIS package is located.

I am not sure about the internal system tables, but yes you can re-work the CACHE by:

DBCC FREEPROCCACHE

DBCC DROPCLEANBUFFERS

read in BOL about more info.

Run this and post the output...

DBCC CHECKDB (databasename) with all_errormsgs