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 |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2002-07-28 : 14:38:22
|
| Sabu writes "I have a table in Sql Server which is about 1.5 gig with over 26 million rows . So what I did is, Created a new DB on a different drive and am planning to move the table. The problem is My log file is taking up so much space, that we will exceed 6GB (data and log...but mostly log) during the transfer. Can I perform an export without writing to the log (LDF) and then essentially turn it on once we are live. Any suggestions on this is greatly appreciated.. Thanks Sabu" |
|
|
setbasedisthetruepath
Used SQL Salesman
992 Posts |
Posted - 2002-07-28 : 23:18:59
|
| A few questions:(1) Did you move the table purely for space reasons? If so, you didn't need to create a new database - you could have defined a new filegroup for the existing database and transferred the table to the new filegroup. Much easier since you will now have to change code to reference the table in the new database.(2) By mentioning 6Gb specifically, should I infer that you've already done the transfer? If so, what method did you use? DTS? BCP? Bulk insert? DML?(3) What recovery model have you specified for the two databases?The short answer to your question is: if you are using bulk methods (bulk insert/bcp) and you do not have the full recovery model specified, you will not incur substantial log writes. If you are using DML to transfer the entire table in one transaction, you will incur the log writes and there is no way around it.Jonathan Boott, MCDBA |
 |
|
|
|
|
|
Transfer a huge table to a new DB