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 |
|
digitall
Starting Member
1 Post |
 Posted - 2008-11-18 : 09:43:23
|
| At my office we had a user accidentally overwrite a few tables with a drop/create script. I was able to find the data via our backups (had to pull from tape) but I couldn't do a straight restore as legit changes had been made since then. The restoration script was approximately 2GB in size and Management Studio (2005/2008) wouldn't open this file natively (even on a system with 8GB ram) and when writing a simple .Net console app to read the file and execute the script it would say the system was out of memory. What is the best way to do a selective restore of a few tables that equate to a couple GB worth of data? The only method I've found thus far is open the script in Notepad2, select 10k-20k lines, paste, execute, repeat (out of almost 400k lines). This is rather tedious though and I'm sure there's a better option. |
|
|
darkdusky
Aged Yak Warrior
591 Posts |
Posted - 2008-12-02 : 05:22:46
|
| You could restore entire database to a different machine or with a new name to same machine from the backup file, then restore individual tables from the database rather than the backups, either using T-SQl or data import wizard. |
 |
|
|
|
|
|
Large Data Restoration