Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
kshahzad
Starting Member
45 Posts |
 Posted - 2013-07-11 : 16:55:10
|
| we have a table with 16 Million records,and also this table is replicated.we want to add a new column in to this table for some reason?what can harm? |
|
|
James K
Master Smack Fu Yak Hacker
3873 Posts |
Posted - 2013-07-11 : 17:05:14
|
| My experience has been that if you add a nullable column (with no default), it is almost instantaneous. But, if you add a column that has to be populated, it will take a bit of time because it will have to go and write all that data. This is from a year or so ago, so I may not be remembering the details precisely. Please do a test for yourself in a dev environment before you take the plunge.As for replication, you should not have to do anything special. See here for details: http://technet.microsoft.com/en-us/library/ms151870.aspx Don't add the column from the GUI, use a T-SQL script with ALTER TABLE. |
 |
|
|
|
|
|
Adding new column to the table that 16 million row