|
|
|
SSC Veteran
      
Group: General Forum Members
Last Login: Saturday, May 18, 2013 11:12 AM
Points: 285,
Visits: 1,377
|
|
|
|
|
|
SSC Veteran
      
Group: General Forum Members
Last Login: Friday, May 17, 2013 6:14 AM
Points: 238,
Visits: 900
|
|
Solomon, this is a great post and thanks for sharing! Just this last week I took a similar approach with 4 large tables that had multiple columns being changed from varchar to nvarchar to support our localization effort. Much of the techniques you mention here were used with the exception of triggers. Given that we were on SQL Server 2008 I was able to use Change Tracking in place of triggers which resulted in 0 modifications to the existing tables. I'd be interested to hear how other folks have used Change Tracking or Change Data Capture. Thanks again for sharing!
Luke C MCP, MCTS, MCITP - Database Administrator & Database Developer
|
|
|
|
|
Forum Newbie
      
Group: General Forum Members
Last Login: Friday, August 03, 2012 6:18 AM
Points: 1,
Visits: 70
|
|
| If Suppose i have 1 Billion Records in the Table. what is the time complexity. Could you please explain the time complexity.
|
|
|
|
|
SSC Rookie
      
Group: General Forum Members
Last Login: Monday, April 09, 2012 9:16 AM
Points: 33,
Visits: 31
|
|
| This is a very good article . My Client here would do enahancements to the application frequently and I end up adding columns to the table with over 3 million rows. Any suggestions how I would do in this scenario?
|
|
|
|
|
SSCertifiable
       
Group: General Forum Members
Last Login: Tuesday, May 14, 2013 4:39 PM
Points: 6,260,
Visits: 1,977
|
|
The article was well explained and straight to the point. The title on the other hand is *VERY* misleading (seconds?) Apparently you don't count the time you spent setting AND processing it all ... 
* Noel
|
|
|
|
|
SSC Veteran
      
Group: General Forum Members
Last Login: Saturday, May 18, 2013 11:12 AM
Points: 285,
Visits: 1,377
|
|
Luke C (4/26/2011) Solomon, this is a great post and thanks for sharing! Just this last week I took a similar approach with 4 large tables that had multiple columns being changed from varchar to nvarchar to support our localization effort. Much of the techniques you mention here were used with the exception of triggers. Given that we were on SQL Server 2008 I was able to use Change Tracking in place of triggers which resulted in 0 modifications to the existing tables. I'd be interested to hear how other folks have used Change Tracking or Change Data Capture.
Hey Luke. Thanks! CDC is an interesting option that I did not think of due to us being on SQL Server 2005. But if I get the chance (someday ), I will revise this article with that option.
Take care, Solomon...
SQL# - http://www.SQLsharp.com/
|
|
|
|
|
SSC Veteran
      
Group: General Forum Members
Last Login: Saturday, May 18, 2013 11:12 AM
Points: 285,
Visits: 1,377
|
|
sathishsathish81 (4/26/2011) If Suppose i have 1 Billion Records in the Table. what is the time complexity. Could you please explain the time complexity.
Hello. The amount of time it takes to move the data over varies based on several factors:
1) How wide is each row 2) How much activity/contention is there on the table 3) How fast is the underlying disk subsystem 4) etc?
So it really takes some testing on each system to really have a decent idea.
Take care, Solomon...
SQL# - http://www.SQLsharp.com/
|
|
|
|
|
SSC Veteran
      
Group: General Forum Members
Last Login: Saturday, May 18, 2013 11:12 AM
Points: 285,
Visits: 1,377
|
|
jvrakesh-858370 (4/26/2011) This is a very good article . My Client here would do enahancements to the application frequently and I end up adding columns to the table with over 3 million rows. Any suggestions how I would do in this scenario?
Hello. I don't really understand your question. Can you please explain in more detail? Thanks.
Take care, Solomon...
SQL# - http://www.SQLsharp.com/
|
|
|
|
|
SSC Veteran
      
Group: General Forum Members
Last Login: Saturday, May 18, 2013 11:12 AM
Points: 285,
Visits: 1,377
|
|
noeld (4/26/2011)
The article was well explained and straight to the point. The title on the other hand is *VERY* misleading (seconds?) Apparently you don't count the time you spent setting AND processing it all ... 
Hi Noel. I am sorry if you feel it was misleading, but I did address this in my article at the beginning of the Overview section. The main intent of the "quickly" making changes was to minimize customer / system impact. The end result is that from the outside (and from the perspective of the application), the restructuring does indeed take only seconds. I also stated in the article summary that this is a way to make large-scale changes that do not require a down-time or maintenance window.
Take care, Solomon...
SQL# - http://www.SQLsharp.com/
|
|
|
|
|
SSC Eights!
      
Group: General Forum Members
Last Login: Tuesday, April 09, 2013 1:20 PM
Points: 936,
Visits: 1,184
|
|
Excellent stuff and very detailed. Thanks for sharing. I have done something similar in the past but never thought of using triggers, instead compared the data between old and new table quickly using Red-Gate data compare tool. But I guess using the Change tracking feature makes it even more convenient.
Thanks!
Amol Naik
|
|
|
|