(mi*******@gmail.com) writes:
I pretty much want to be able to look at a .mdf file to see what could
be mangled in it.
If your database is corrupt so that you cannot easily repair it with
DBCC, you should open a case with Microsoft. Editing the internal
structures of database file will just mangle it even more.
If for some reason the application that writes to the database gives an
error because of invalid character or something in a certain field i
would like to see what field it is and what's in it. Simply attaching it
does me no good.
Your application cannot on its own corrupt the database. It would
need help from either a bug in SQL Server or bad hardware.
If your application produces an error message, you should first use the
Profiler to find where what statements the application is sending. Once
there you can run the queries in Query Analyzer. In QA you can run commands
like sp_help to see the definition of tables and constraints etc.
My guess is that you run a third-party app. In such, you should open a
support case with that vendor.
--
Erland Sommarskog, SQL Server MVP,
es****@sommarskog.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinf...2000/books.asp