Trouble after migrating to a 2005 clustered environment -- sql server clustering

Moishe Much
8/29/2007 1:44:03 PM

We just migrated a large database from SQL 2000 ent ed. to SQL 2005 ent. ed.
This migration included moving to larger, faster hardware on an
active-passive clustered pair of Win 2003 servers (32 GB RAM, quad
processors, etc).

Once the migration & compatibility changes to the database were complete, we
found that many of our queries and inserts that ran quickly and well on the
old 2000 system now take excessive amounts of time to run in the newer,
larger, faster, clustered environment. Queries and inserts that ran in a
minute or less take two hours or more to complete now.

We're baffled by this, since it seems to indicate that in a larger, faster,
clustered environment, SQL 2005 may require us to go back and custom tune
hundreds of queries and inserts.

Have you experienced this or know why SQL Server 2005 would perform so
poorly in a newer, larger, faster clustered environment?

Regards

(JR) Jorge Rivera
8/29/2007 5:08:02 PM

Hi

We need more info, about mem, disk and pro usage ..
but meanwhile you can do the next step :
Trace the slow querys, and use database engine tunign advisor to fix it...
If the query( or the structure) is the same all times, may be there is a
document explaining the behaivor.. an you can find in MSFT KB

[quoted text, click to view]

Tom Moreau
8/29/2007 5:58:11 PM

Did you update statistics WITH FULLSCAN after the migration?

--
Tom

----------------------------------------------------
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau

[quoted text, click to view]
We just migrated a large database from SQL 2000 ent ed. to SQL 2005 ent. ed.
This migration included moving to larger, faster hardware on an
active-passive clustered pair of Win 2003 servers (32 GB RAM, quad
processors, etc).

Once the migration & compatibility changes to the database were complete, we
found that many of our queries and inserts that ran quickly and well on the
old 2000 system now take excessive amounts of time to run in the newer,
larger, faster, clustered environment. Queries and inserts that ran in a
minute or less take two hours or more to complete now.

We're baffled by this, since it seems to indicate that in a larger, faster,
clustered environment, SQL 2005 may require us to go back and custom tune
hundreds of queries and inserts.

Have you experienced this or know why SQL Server 2005 would perform so
poorly in a newer, larger, faster clustered environment?

Regards

Got something to say? Click here to post a reply to this thread.

Don't see what you're looking for? Try a search.

View other messages about sql server clustering

sql server clustering : Trouble after migrating to a 2005 clustered environment