January 27, 2009 at 10:54 am
Has anyone had experience with the SQL Server Upgrade Assistant?
I want to use it as part of an effort to upgrade existing SQL 2000 and SQL 2005 instances in our environment.
Here is the link:
http://www.scalabilityexperts.com/default.asp?action=article&ID=90
__________________________________________________________________________________
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]
January 27, 2009 at 11:29 am
Yeah, I used it at a lab at the Microsoft Technology Center to test the upgrade of one of our databases. I blogged about it here[/url].
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
January 27, 2009 at 11:37 am
Grant Fritchey (1/27/2009)
Yeah, I used it at a lab at the Microsoft Technology Center to test the upgrade of one of our databases. I blogged about it here[/url].
Thanks! I will check it out...
__________________________________________________________________________________
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]
January 27, 2009 at 11:44 am
Grant Fritchey (1/27/2009)
Yeah, I used it at a lab at the Microsoft Technology Center to test the upgrade of one of our databases. I blogged about it here[/url].
Restoring the system dbs...
What does that entail? Is it done transparently by the tool or is there anything manual that needs to be done?
When I read about a system-db restore, nightmarish memories come to mind, memories I'd rather keep pushed deep down in the subconscious...
__________________________________________________________________________________
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]
January 27, 2009 at 11:48 am
Marios Philippopoulos (1/27/2009)
Restoring the system dbs...What does that entail? Is it done transparently by the tool or is there anything manual that needs to be done?
When I read about a system-db restore, nightmarish memories come to mind, memories I'd rather keep pushed deep down in the subconscious...
Yeah, I know exactly what you mean. I have those nightmares too.
No, it went flawlessly. Now, I did this on a test system and I had MS support people hovering in the room with me, but I didn't even need them. Getting the database ID's correct for the playback was the biggest problem I ran into.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
January 27, 2009 at 12:06 pm
Grant Fritchey (1/27/2009)
Marios Philippopoulos (1/27/2009)
Restoring the system dbs...What does that entail? Is it done transparently by the tool or is there anything manual that needs to be done?
When I read about a system-db restore, nightmarish memories come to mind, memories I'd rather keep pushed deep down in the subconscious...
Yeah, I know exactly what you mean. I have those nightmares too.
No, it went flawlessly. Now, I did this on a test system and I had MS support people hovering in the room with me, but I didn't even need them. Getting the database ID's correct for the playback was the biggest problem I ran into.
Thanks, after reading your blog, it seems that several pieces need to fall into place for this to run smoothly.
For one, there needs to be tight coordination between the testing/QA teams and the DBA team, so that a proper/representative workload is created. I was - naively - thinking of having the tool run for a few days and capture the workload for playback, but that would generate way too much data.
The thing I didn't like the most though was the recommendation by MS that a single user thread for testing be used. That means - in my circumstances - that a totally separate testing cycle, apart from our regular QA cycle, be used. We don't have enough resources for this sort of thing.
I still need to do more research on this, but it seems this tool is a lot harder to use than I originally thought...
__________________________________________________________________________________
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]
January 27, 2009 at 12:39 pm
The single thread on the user app is because the tool using Profiler for the playback. Profiler isn't smart enough to spawn a different process for each SPID as it encounters them. That's why you have to have just one guy run the tests. It's a pain, but it makes it possible to easily capture and playback a realistic workload.
I think there are third party tools out there that can take a trace and spawn threads as appropriate, but I've never used one, so I can't really recommend any.
It did require a bit of work to set up, but I was very happy with the results. I'm planning on putting as many of our upgrades as I can through the process. I doubt all of them will sit still long enough to generate single-threaded tests and then wait for the playback, but we'll see.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply