January 31, 2013 at 6:43 am
We just recieved new ip2Location data. it appears our old one is a few years old. i need to basically replace the existing w/ this new one.
I was planning on building indexes on the new one then switching the names. Rename the old version and then rename the new one to what the old one was.
My question is. Is there a better way to do this sort of thing w/o affecting the clients? As you can imaging this table is getting hammered.
Ideas?
January 31, 2013 at 2:11 pm
Snargables (1/31/2013)
We just recieved new ip2Location data. it appears our old one is a few years old. i need to basically replace the existing w/ this new one.I was planning on building indexes on the new one then switching the names. Rename the old version and then rename the new one to what the old one was.
My question is. Is there a better way to do this sort of thing w/o affecting the clients? As you can imaging this table is getting hammered.
Ideas?
Pretty vague but that sounds like a reasonable way to handle this. Of course the object here is to minimize downtime. The approach you outlined should make it very fast.
_______________________________________________________________
Need help? Help us help you.
Read the article at http://www.sqlservercentral.com/articles/Best+Practices/61537/ for best practices on asking questions.
Need to split a string? Try Jeff Modens splitter http://www.sqlservercentral.com/articles/Tally+Table/72993/.
Cross Tabs and Pivots, Part 1 – Converting Rows to Columns - http://www.sqlservercentral.com/articles/T-SQL/63681/
Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs - http://www.sqlservercentral.com/articles/Crosstab/65048/
Understanding and Using APPLY (Part 1) - http://www.sqlservercentral.com/articles/APPLY/69953/
Understanding and Using APPLY (Part 2) - http://www.sqlservercentral.com/articles/APPLY/69954/
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply