April 23, 2008 at 2:07 pm
I have a SQL 2000 instance which I am upgrading to SQL 2005, and I would like to run the Upgrade Advisor on that instance prior to upgrading.
Should I install the SQL 2005 Upgrade Advisor locally on that server, or would running it remotely from my own desktop be OK? My computer and the server to be upgraded are on the same domain but are far removed geographically, so some network latency is involved.
Any performance considerations I should be aware of while running the advisor? Will it cause locking/contention in the databases while running?
__________________________________________________________________________________
SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
Persisting SQL Server Index-Usage Statistics with MERGE[/url]
Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]
April 23, 2008 at 3:11 pm
I have always run it locally no problem and prefer that, but you can run remotely I believe.
It is very light on the server, no performance hit
HTH
---------------------------------------------------------------------
April 23, 2008 at 3:53 pm
I installed it on my workstation and ran it against all of our SQL Server instances over the network. It had no noticeable affect on performance of either the servers or my PC, but the more objects it has to look at, the longer it takes.
Greg
April 24, 2008 at 9:43 am
thanks guys, much appreciated.
__________________________________________________________________________________
SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
Persisting SQL Server Index-Usage Statistics with MERGE[/url]
Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply