Validates the contents of every indexed view in the database.
Validates link-level consistency between table metadata and file system directories and files when storing varbinary(max) data in the file system using FILESTREAM.
Validates the Service Broker data in the database.
This means that the DBCC CHECKALLOC, DBCC CHECKTABLE, or DBCC CHECKCATALOG commands do not have to be run separately from DBCC CHECKDB. For more detailed information about the checks that these commands perform, see the descriptions of these commands.
I think David's reply is a perfect answer for the original question (which tools uses NMM to perform consistency check of SQL DB's), however it didn't explain how NMM uses those SQL tools to perform consistency check during an NMM backup process.
Basically, as in the case of Exchange backups, NMM, through ReplicationManager module uses ESE util to perform the consistency check of the DB on the snapshot mounted, previously taken by NMM /Exchange Writer or SQL writer). For SQL will use the tools mentioned by David in his previous answer.
Once Snapshot is mounted Replication manager will use the native tool of the DB's to perform the consistency check.
Please let me know if this answered your question or if you need any further informaiton.
i think the question is how the networker module for microsoft applications (NMM) does the consistancy check when doing backups. not HOW TO do it within MSSQL in general.
Yes, the original question is "What utility is used by NMM to perform the SQL DB consistency checks". The admin guide is very clear about MS Exchange but not clear about the SQL , since DBCC is not an internal SQL command like eseutil is, it needs a clarification.
praviad
21 Posts
0
August 27th, 2010 02:00
Checks the logical and physical integrity of all the objects in the specified database by performing the following operations:
Runs DBCC CHECKALLOC on the database.
Runs DBCC CHECKTABLE on every table and view in the database.
Runs DBCC CHECKCATALOG on the database.
Validates the contents of every indexed view in the database.
Validates link-level consistency between table metadata and file system directories and files when storing varbinary(max) data in the file system using FILESTREAM.
Validates the Service Broker data in the database.
This means that the DBCC CHECKALLOC, DBCC CHECKTABLE, or DBCC CHECKCATALOG commands do not have to be run separately from DBCC CHECKDB. For more detailed information about the checks that these commands perform, see the descriptions of these commands.
Cheers
David S Pravia
36115_carloscor
217 Posts
0
August 27th, 2010 07:00
Hi there Jejje,
I think David's reply is a perfect answer for the original question (which tools uses NMM to perform consistency check of SQL DB's), however it didn't explain how NMM uses those SQL tools to perform consistency check during an NMM backup process.
Basically, as in the case of Exchange backups, NMM, through ReplicationManager module uses ESE util to perform the consistency check of the DB on the snapshot mounted, previously taken by NMM /Exchange Writer or SQL writer). For SQL will use the tools mentioned by David in his previous answer.
Once Snapshot is mounted Replication manager will use the native tool of the DB's to perform the consistency check.
Please let me know if this answered your question or if you need any further informaiton.
Thank you.
Carlos.
Jejje1
13 Posts
0
August 27th, 2010 07:00
i think the question is how the networker module for microsoft applications (NMM) does the consistancy check when doing backups. not HOW TO do it within MSSQL in general.
FlyEagles
1 Rookie
•
23 Posts
0
August 27th, 2010 08:00
Thanks for your replies.
Yes, the original question is "What utility is used by NMM to perform the SQL DB consistency checks". The admin guide is very clear about MS Exchange but not clear about the SQL , since DBCC is not an internal SQL command like eseutil is, it needs a clarification.
FlyEagles
1 Rookie
•
23 Posts
0
September 7th, 2010 14:00
Just wanted to give an update. According to Engineering team, this is a document bug. NMM does not perform any consistency check with SQL backups.