There is no good reason to put up with persistent lying. I certainly agree there.

This should be enough to get you going.

FROMtblVoucherDetails IDETAIL

Inner Join tblVoucherGroup PACKAGE

On Package.RegionID = IDetail.RegionID

AND IDETAIL.VoucherNumber = PACKAGE.VoucherNumber

AND IDETAIL.PackageID = PACKAGE.GroupID

/*Inner Join tblChargeType CHARGE

On Charge.ChargeTypeID *= Idetail.ChargeTypeID...

NP.

Jeff Moden (4/5/2010)

---

Heh... I love it when they...

Yes you could do that.

Unless these packages are interdependent, then each package only overwrites it's respective package in MSDB.

Start by posting the table definitions for the tables involved with Keys on those tables.

bitbucket-25253 (4/5/2010)

---

Follow the first link in my signature block to post the table's definitions, including indexes (if any), column constraints (if any). Without knowing the details about the table...

I think I might be considerably surprised as well.

That will be the day. Carry your OS around on a flashdrive, plug into any computer and immediately have all of your settings and apps. Would be extremely...

I would go with the DDL triggers and audit the database in that regard. This would help ensure that the pertinent action is recorded.

Here is some info that may be of use.

http://searchsqlserver.techtarget.com/expert/KnowledgebaseAnswer/0,289625,sid87_gci1118005,00.html?bucket=ETA&topic=301323

I have never done it before, but it looks like you can do it with the built in SQL 2005 stuff. ...

I agree with Paul. Start with breaking out the DB backups to separate jobs.

It appears that you are going the wrong direction with that. You have a SQL 2005 database trying to restore to a SQL 2000 Instance - not possible.

Please provide your table definitions, and what queries you have tried so far.

This will be more helpful and more consumable by the community trying to help you.