When I did the upsize wizard, for the relationships, I
thought it was set to DRI. However, it was set to
Triggers.

I have since moved my access XP tables to SQL 2k tables
and the data.

Should it be an issue that the relationships are in
Triggers, not DRI?

Should I try to fix that? If so, what's the easiest way?

I was thinking of creating a new sql db (dbnew) and
upsizing the access tables without the data and making
sure it uses DRI. Then I would use DTS to import data
from the current SQL db (dbcurrent) to the new one. Then
I would delete the current SQL db (dbcurrent).

Finally, I would again create another SQL db with the
original name (dbcurrent), upsize the tables without hte
data...and then re-import the data back from dbnew. Then
deleting the dbnew. Therefore, I have the dbcurrent with
the DRI and my data would be current.

A lil crazy, but is there an easier way of doing this?

DRI would definitely be easier to maintain, and most likely perform better
as well.

I think the easiest scenario is to use the upsize wizard to create a new
database with DRI without the data. Then generate a script in Enterprise
Manager for the tables in the new database with all options on (third tab in
the wizard) and remove everything except the statements that create the
foreign keys. Next generate a script on the original database for all tables
and triggers with the option "generate the DROP command for each object".
Remove everything from that that doesn't relate to triggers. Finally run the
triggers script and then the foreign keys script. (And back up your original
database before you start).

--
Jacco Schalkwijk
SQL Server MVP


"Ngan" <anonymous (AT) discussions (DOT) microsoft.com> wrote