Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
bryan42
Starting Member
28 Posts |
 Posted - 2007-03-05 : 14:13:40
|
| Starting with a SQL Server 2000 database, my company built a new server with SQL Server 2005 and restored the SS2000 database from backups. We're now seeing some extreme issues where queries that took 30 seconds now take 3 minutes. Would this make you suspect index issues? Any recommendations on diagnosing and fixing this would be appreciated. |
|
|
graz
Chief SQLTeam Crack Dealer
4149 Posts |
Posted - 2007-03-05 : 14:19:29
|
| You definitely need to rebuild the indexes when you migrate from SQL Server 2000 to 2005. There's an article on the front page right now where I mention this.===============================================Creating tomorrow's legacy systems today.One crisis at a time. |
 |
|
|
bryan42
Starting Member
28 Posts |
Posted - 2007-03-05 : 14:29:10
|
| Thanks much! That article is helpful. Could you tell me how to perform these add tasks mentioned there?>"We also ran DBCC UPDATEUSAGE and sp_updatestats on the database." |
|
|
|
graz
Chief SQLTeam Crack Dealer
4149 Posts |
Posted - 2007-03-05 : 14:53:07
|
| You'll need to check Books Online for the correct syntax but I'm 99% sure it's justDBCC UPDATEUSAGE andEXEC sp_updatestats -Bill===============================================Creating tomorrow's legacy systems today.One crisis at a time. |
|
|
|
propanecan
Yak Posting Veteran
60 Posts |
Posted - 2007-03-05 : 17:37:55
|
| This perhaps?sp_spaceused @updateusage = true |
|
|
|
|
|
|
Can migration lead to index problems?