SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


SQL Server Cloud Migration Part I


SQL Server Cloud Migration Part I

Author
Message
Edward.Polley 76944
Edward.Polley 76944
Old Hand
Old Hand (380 reputation)Old Hand (380 reputation)Old Hand (380 reputation)Old Hand (380 reputation)Old Hand (380 reputation)Old Hand (380 reputation)Old Hand (380 reputation)Old Hand (380 reputation)

Group: General Forum Members
Points: 380 Visits: 264
Comments posted to this topic are about the item SQL Server Cloud Migration Part I
Andy Warren
Andy Warren
SSC Guru
SSC Guru (52K reputation)SSC Guru (52K reputation)SSC Guru (52K reputation)SSC Guru (52K reputation)SSC Guru (52K reputation)SSC Guru (52K reputation)SSC Guru (52K reputation)SSC Guru (52K reputation)

Group: Moderators
Points: 52076 Visits: 2795
Edward, I'm not sure I follow on the velocity calculation - it looks like you're only measuring new rows and not changes to existing rows?

Andy
SQLAndy - My Blog!
Connect with me on LinkedIn
Follow me on Twitter
TGwinn
TGwinn
SSC-Enthusiastic
SSC-Enthusiastic (132 reputation)SSC-Enthusiastic (132 reputation)SSC-Enthusiastic (132 reputation)SSC-Enthusiastic (132 reputation)SSC-Enthusiastic (132 reputation)SSC-Enthusiastic (132 reputation)SSC-Enthusiastic (132 reputation)SSC-Enthusiastic (132 reputation)

Group: General Forum Members
Points: 132 Visits: 464
Andy Warren (9/23/2013)
Edward, I'm not sure I follow on the velocity calculation - it looks like you're only measuring new rows and not changes to existing rows?


I was wondering the same thing.
Edward.Polley 76944
Edward.Polley 76944
Old Hand
Old Hand (380 reputation)Old Hand (380 reputation)Old Hand (380 reputation)Old Hand (380 reputation)Old Hand (380 reputation)Old Hand (380 reputation)Old Hand (380 reputation)Old Hand (380 reputation)

Group: General Forum Members
Points: 380 Visits: 264
Hi Andy:

Yes - ours is a high insert OLTP environment, percentage of updates on our systems is low so for this migration it didn't matter. But tracking updates is a good point, if I had to do that I would examine the 'last_update' column on critical tables, failing that I'd look at sampling traces.
JayK
JayK
SSCommitted
SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)

Group: General Forum Members
Points: 1559 Visits: 1133
Hey Edward,

I am currently upgrading our SQL Server 2008 R2 environment to SQL Server 2012 on all new Windows 2012 servers so found this very interesting - sounds like a very well managed migration.

Can I just ask if you weren't keeping track of updates, how did you mitigate against lost data? Even if the amount of updates are small in our DB's if you were only syncing new records how did you get by without holding the history of the updates?

Cheers,
JayK
Edward.Polley 76944
Edward.Polley 76944
Old Hand
Old Hand (380 reputation)Old Hand (380 reputation)Old Hand (380 reputation)Old Hand (380 reputation)Old Hand (380 reputation)Old Hand (380 reputation)Old Hand (380 reputation)Old Hand (380 reputation)

Group: General Forum Members
Points: 380 Visits: 264
In the process of analyzing the data I focused on inserts/deletes as that is how our system are designed, in the actual migration on the critical high volume DBs I synched all data using full backup/restore + Tlogs. These critical DBs are where the business makes money so couldn't lose any data. On the less critical or lower volume tables I used a one time backup/restore weeks in advance of the migration followed by redgate data compare scripts - DC allows you to customize what data to synchronize. These scripts are the key as they allow you to setup jobs to synch hundreds of tables. No data was lost other than several tlogs failed to restore at 2 am.:-)

Note that tables without primary keys or unique indexes need a bit of testing in Redgate to ensure they are coded correctly.

I spent a lot of time analyzing our data insert/update/delete/select pattern before deciding updates weren't a significant part of our production process. Your site might be very different.

Recommend you plan for missing data and let management know what to expect - it took about a week or so to clean up security, indexes and some less critical reporting tables - but the business was up in and making money in just a few hours and that is what I was after.
JayK
JayK
SSCommitted
SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)

Group: General Forum Members
Points: 1559 Visits: 1133
Hey Ed - Ok - that makes sense - thanks for sharing your experience with us - definite food for thought for my own work:-)
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum







































































































































































SQLServerCentral


Search