I need Proof!

Not the alcohol kind!!
We're log shipping from one db to another in SQL 2000 and when I turn off
log shipping and move to the new server I need to be able to prove that the
two DB copies are identical bit for bit.
Is there an internal change number that I can get at with this info. Oracle
calls it the system change number.
We cannot for auditing reasons do things like: visually inspect tables,
create a final table and verify it gets applied, drop an object and once it's
dropped on the recipient move forward. Because of our Financial system
requirements, think Sarbanes Oxley, I need to be able to PROVE it with a
command, not something else.
That said, can anyone help? I thought dbcc dbinfo might do it but it
doesn't appear to be the case.
Many thanks!!!!
--
burt_king@.yahoo.comHmmm...you can check the status (success) and time/date for the t-log
backup, copy and restore jobs. Or if needed perhaps a third-party data
comparision tool like RedGate's Data Compare or ApexSQL's Diff tool.
HTH
Jerry
"burt_king" <burt_king@.yahoo.com> wrote in message
news:5EA89F29-EA3F-4793-ADD2-54411D06FE02@.microsoft.com...
> Not the alcohol kind!!
> We're log shipping from one db to another in SQL 2000 and when I turn off
> log shipping and move to the new server I need to be able to prove that
> the
> two DB copies are identical bit for bit.
> Is there an internal change number that I can get at with this info.
> Oracle
> calls it the system change number.
> We cannot for auditing reasons do things like: visually inspect tables,
> create a final table and verify it gets applied, drop an object and once
> it's
> dropped on the recipient move forward. Because of our Financial system
> requirements, think Sarbanes Oxley, I need to be able to PROVE it with a
> command, not something else.
> That said, can anyone help? I thought dbcc dbinfo might do it but it
> doesn't appear to be the case.
> Many thanks!!!!
> --
> burt_king@.yahoo.com|||copy and restore are proof enough for me,,,, but not the company. I need to
run a command which says, "what's the current version of the database?" and
both the source and destination should be the same.
--
burt_king@.yahoo.com
"Jerry Spivey" wrote:
> Hmmm...you can check the status (success) and time/date for the t-log
> backup, copy and restore jobs. Or if needed perhaps a third-party data
> comparision tool like RedGate's Data Compare or ApexSQL's Diff tool.
> HTH
> Jerry
> "burt_king" <burt_king@.yahoo.com> wrote in message
> news:5EA89F29-EA3F-4793-ADD2-54411D06FE02@.microsoft.com...
> > Not the alcohol kind!!
> >
> > We're log shipping from one db to another in SQL 2000 and when I turn off
> > log shipping and move to the new server I need to be able to prove that
> > the
> > two DB copies are identical bit for bit.
> >
> > Is there an internal change number that I can get at with this info.
> > Oracle
> > calls it the system change number.
> >
> > We cannot for auditing reasons do things like: visually inspect tables,
> > create a final table and verify it gets applied, drop an object and once
> > it's
> > dropped on the recipient move forward. Because of our Financial system
> > requirements, think Sarbanes Oxley, I need to be able to PROVE it with a
> > command, not something else.
> >
> > That said, can anyone help? I thought dbcc dbinfo might do it but it
> > doesn't appear to be the case.
> >
> > Many thanks!!!!
> > --
> > burt_king@.yahoo.com
>
>|||Like Jerry said, your best bet is probably a third-party tool for an
extremely strict data versioning requirement like that.
"burt_king" <burt_king@.yahoo.com> wrote in message
news:04BEEA1F-7FB3-4095-A784-870A95A6F0C4@.microsoft.com...
> copy and restore are proof enough for me,,,, but not the company. I need
> to
> run a command which says, "what's the current version of the database?"
> and
> both the source and destination should be the same.
> --
> burt_king@.yahoo.com
>
> "Jerry Spivey" wrote:
>> Hmmm...you can check the status (success) and time/date for the t-log
>> backup, copy and restore jobs. Or if needed perhaps a third-party data
>> comparision tool like RedGate's Data Compare or ApexSQL's Diff tool.
>> HTH
>> Jerry
>> "burt_king" <burt_king@.yahoo.com> wrote in message
>> news:5EA89F29-EA3F-4793-ADD2-54411D06FE02@.microsoft.com...
>> > Not the alcohol kind!!
>> >
>> > We're log shipping from one db to another in SQL 2000 and when I turn
>> > off
>> > log shipping and move to the new server I need to be able to prove that
>> > the
>> > two DB copies are identical bit for bit.
>> >
>> > Is there an internal change number that I can get at with this info.
>> > Oracle
>> > calls it the system change number.
>> >
>> > We cannot for auditing reasons do things like: visually inspect tables,
>> > create a final table and verify it gets applied, drop an object and
>> > once
>> > it's
>> > dropped on the recipient move forward. Because of our Financial
>> > system
>> > requirements, think Sarbanes Oxley, I need to be able to PROVE it with
>> > a
>> > command, not something else.
>> >
>> > That said, can anyone help? I thought dbcc dbinfo might do it but it
>> > doesn't appear to be the case.
>> >
>> > Many thanks!!!!
>> > --
>> > burt_king@.yahoo.com
>>|||try
DBCC fileheader [( {'dbname' | dbid} [, fileid])
--
Aleksandar Grbic
"burt_king" wrote:
> Not the alcohol kind!!
> We're log shipping from one db to another in SQL 2000 and when I turn off
> log shipping and move to the new server I need to be able to prove that the
> two DB copies are identical bit for bit.
> Is there an internal change number that I can get at with this info. Oracle
> calls it the system change number.
> We cannot for auditing reasons do things like: visually inspect tables,
> create a final table and verify it gets applied, drop an object and once it's
> dropped on the recipient move forward. Because of our Financial system
> requirements, think Sarbanes Oxley, I need to be able to PROVE it with a
> command, not something else.
> That said, can anyone help? I thought dbcc dbinfo might do it but it
> doesn't appear to be the case.
> Many thanks!!!!
> --
> burt_king@.yahoo.com|||DBCC fileheader doesn't appear to match the two for a log shipping server.
Sorry.
--
burt_king@.yahoo.com
"Aleksandar Grbic" wrote:
> try
> DBCC fileheader [( {'dbname' | dbid} [, fileid])
> --
> Aleksandar Grbic
>
> "burt_king" wrote:
> > Not the alcohol kind!!
> >
> > We're log shipping from one db to another in SQL 2000 and when I turn off
> > log shipping and move to the new server I need to be able to prove that the
> > two DB copies are identical bit for bit.
> >
> > Is there an internal change number that I can get at with this info. Oracle
> > calls it the system change number.
> >
> > We cannot for auditing reasons do things like: visually inspect tables,
> > create a final table and verify it gets applied, drop an object and once it's
> > dropped on the recipient move forward. Because of our Financial system
> > requirements, think Sarbanes Oxley, I need to be able to PROVE it with a
> > command, not something else.
> >
> > That said, can anyone help? I thought dbcc dbinfo might do it but it
> > doesn't appear to be the case.
> >
> > Many thanks!!!!
> > --
> > burt_king@.yahoo.com