Viewing 15 posts - 16 through 30 (of 104 total)
was there a reboot after uninstallation?.
April 23, 2010 at 12:17 pm
Check for logs in event viewer, you might find some information there.
April 20, 2010 at 9:52 am
No need to run any upgrade scripts.But do test in your test environment before upgrading to SP3 in production to make sure applications are compatible with SP3.
April 19, 2010 at 1:20 pm
If this is Sql Server 2005, there will be default trace running.You might find more information there.
April 19, 2010 at 1:13 pm
no, it will not upgrade SSIS Packages.
March 15, 2010 at 2:51 pm
you have to upgrade ssis packages,recreate all SQL Agent jobs,setup db mail,rebuild index and update stas with full scan,recreate alerts and warnings,enable all startup proc`s and run dbcc checkdb on...
March 15, 2010 at 12:16 pm
After inplace upgrade..you need to change compatibility mode to 100 manually.
March 15, 2010 at 11:46 am
Redgate SQL Compare
February 25, 2010 at 10:13 am
my guess is you did an inplace upgrade...can you tell what steps have you performed after the upgrade?.
February 25, 2010 at 9:32 am
Have you done rebuild index and update stats?
February 25, 2010 at 7:43 am
For inplace upgrade to SQL 2008, your SQL 2000 must be at SP4 or above.
February 19, 2010 at 7:29 am
check the job history.In case any of the scheduled jobs failed during this power failure and you can run them again.
February 8, 2010 at 9:56 am
Rudy..Did the unattended sp3 install worked ?
February 4, 2010 at 9:27 am
Also if you have any SSIS packages which use 32bit drivers for connectivity make sure you have appropriate 64bit drivers.
January 29, 2010 at 8:05 am
Viewing 15 posts - 16 through 30 (of 104 total)