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 |
|
dadoph
Starting Member
1 Post |
 Posted - 2014-05-01 : 13:15:19
|
| Disclaimer: I am not a DBA but have responsibility for a particular MSSQL 2008 R2 file server running a particular application. Trying to figure out how to solve a database consistency check problem.The database fails dbcc checkdb with multiple 8903 errors. Unfortunately this was not discovered until well after any good backups were deleted. The good news is that the DB otherwise seems fine. We have experienced zero problems with the DB or the applications. Running the checkdb with the "repair_allow_data_loss" option does not fix the problem.However, I would still like to fix the problem. Using a popular SQL recovery product I am able to recover the database. Here's my problem:The original, vendor designed and supplied DB, has 2 file groups, and three files (MDF, NDF, LDF). The output of the recovery process produces 1 file group and 2 files (MDF and LDF). Vendor says they cannot support me since the recovered DB is 'non-standard' according to their design.I am able to set up a new, blank version of the vendors database on another dev system with the proper file and filegroup structure. How can I get the data moved/copied from the recovered (MDF/LDF) database into the dev database (MDF, NDF, LDF). I've tried the import/export function but it fails (I can rerun and give details if necessary). Sorry if I'm leaving out something valuable. As I said, not a DBA and not SQL fluent, unfortunately. Thanks in advance for your help. |
|
|
bitsmed
Aged Yak Warrior
545 Posts |
Posted - 2014-05-01 : 18:23:27
|
| You might have a look at "bulk insert" where you leave out the "FIRE_TRIGGERS" and "CHECK_CONSTRAINTS", and after inserting data to all tables, use "alter table xx with check constraint all" on all tables. |
 |
|
|
|
|
|
|
|
DB and Filegroups Questions