Similar Threads:
1.Slow backups after upgrade to Windows Server 2003 SP1
Greetings,
I recently upgraded a server to Windows Server 2003 SP1. The server is
running
SQL Server 2000 SP4 and ARCServe 9.01 SQL Agent.
Transaction Log Backups on this server have slowed down by about 50X.
Throughput has gone from about 300MB/minute to about 6 MB/minute.
I tried upgrading the SQL Agent to ARCServe 9.01 SP1, but that didn't
seem to
help.
I have another server that had Windows Server 2003 installed on it from
the
start, recently upgraded to SP1, running ARCServe 11 SQL Agent. That server
has no problems with backup.
I know this sounds like an ARCServe issue, but I'd like to avoid
upgrading to
ARCServe 11 if I can. Has anyone else seen anything similar? If so, how
did you
work around it?
Regards,
Jonathan
2.Is it imp to upgrade windows 2003 with SP1 before upgrading sql2k
Is there any recommendation that we should upgrade windows 2003 with SP1
first before upgrading SQL server 2000 SP4?
Please let me know if there is any information related to this.
Thanks!
Shriniwas
3.After installing SQL Server 2005 SP1 SSMS cannot connect to the se
4.SSMS 2005 on Vista SP1 can't find new named cluster instance
All,
I have two Vista SP1 machines that have SSMS 2005 installed on them. These
two machines (both used by developers) cannot see my new named SQL cluster
instance when trying to connect using SSMS. Every other PC in the office
with SSMS can find the instance. The two trouble machines can ping the
virtual cluster by name. They just can't pull up the instance in SSMS. Both
developers have permissions to connect to the instance. One developer with a
trouble PC says he can run a query against the instance from the same trouble
PC using Visual Studio 2005. I can't figure out what's going on but I need
to fix this. Any suggestions?
5.SSMS and BI Studio very very slow
1) It takes about 10 seconds for the in-context menu to appear when I
right-click on a table. On subsequent attempts, it appears almost immediately.
2) It takes more than 10 seconds to save a new table design in SSMS (right
click on Tables, New Table..., wait 5 seconds right there, design your table,
click on the floppy icon to save it, and wait 15 seconds)
3) I often get the following message in BI studio "Microsoft Visual Studio
is busy. Microsoft Visual Studio is waiting for an internal operation to
complete. If you regularly encounter the delay during normal usage, please
report the problem to Microsoft". And that shows up when I click on a data
flow transformation in design mode.
4) When I click on the "Start debugging" of an SSIS package, it takes ages
to start executing. The execution itself is really fast (5 million rows in
less than a minute through several transformations)
I have numerous examples of very basic operations that take ages to
complete. What could be possibly going on? I have now turned off the "MS
customer feedback " from the help menu, to no avail.
This has been going on since day one.
I'm working locally on the server with a remote desktop connection, a dual
Xeon with 4 Gig memory, and doing nothing but development. I have verified
that the System Idle Process is above 95% during all the cases indicated
above.
Win 2003 Enterprise edition, SQL Server 2005 Enterprise.
6. Start SSMS error
7. SSMS screen refresh rate very slow
8. Not able to start SSMS using user from Sql server