Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
DB Engine
SQL ServerMSDESQL Server CE
Services
Analysis (Data Mining)Analysis (OLAP)DTSIntegration ServicesNotification ServicesReporting Services
Programming
CLRConnectivitySQLXML
Other Technologies
ClusteringEnglish QueryFull-Text SearchReplicationService Broker
General
Data WarehousingPerformanceSecuritySetupSQL Server ToolsOther SQL Server Topics
DirectoryUser Groups
Related Topics
MS AccessOther DB ProductsMS Server Products.NET DevelopmentVB DevelopmentJava DevelopmentMore Topics ...

SQL Server Forum / DB Engine / SQL Server / July 2008

Tip: Looking for answers? Try searching our database.

After SP4

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Alberto Brivio - 24 Jul 2008 10:45 GMT
Dear ALL,

I have a failover cluster based on win 2000 AS machines and SQL 2000 just
upgraded to SP4 a couple of days ago.

Under normal conditions things seems to be good but when many jobs (dts,
stored procedures and so on) are running together much more time is needed
than in SP3 environment.
So is this a behaviour caused by SP4 and if yes are there any changes to be
applied in order to get the right way?
Another question is, can I do a downgrade to SP3 ?

                                                    Regards

                                                    Alberto Brivio
Uri Dimant - 24 Jul 2008 11:31 GMT
Alberto
I do not think that it is an issue. Have you monitoring your server? How
about the memory?
If you have enabled AWE please make sure that  you have hotfix
from(http://support.microsoft.com/kb/899761)

> Dear ALL,
>
[quoted text clipped - 11 lines]
>
>                                                     Alberto Brivio
Russell Fields - 24 Jul 2008 14:32 GMT
Alberto,

Downgrading to SP3 (if you decide to do it) involves reinstalling SQL Server
2000 and reapplying up to the proper SP and hotfix, then restoring the
master, model, and msdb from before the upgrade.  I believe that is
documented in the installation procedure, but it is a fair amount of work.

I know of one installation where performance problems were fixed by giving
tempdb several files to work with, instead of just one.  In that case, they
made 10 files, based on this KB article:
http://support.microsoft.com/kb/328551/en-us under the subheading "Increase
the number of tempdb data files with equal sizing".

Then there may be problems with indexed views, if you use those.  There is a
fix described at http://support.microsoft.com/kb/906117/en-us

FWIW,
RLF

> Dear ALL,
>
[quoted text clipped - 11 lines]
>
>                                                     Alberto Brivio
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.