Primary keys lost after DTS

after performing export/dts from our database server to our hosting server,
the primary keys of each table in the destination server are lost. using the
dts wizard, i use the third option (copy database objects and data) and i di
d
make sure that the copy primary and foreign keys option is on. Can anyone
tell me how to solve the problem?
BTW, i did experience an error during the DTS process. "SetUser permission
denied." but still all database objects were transfered including the
contents except the primary keys. Does it had something to do with the
database account im using to connect to the server, which i think is limited
?In my own view is most clear generate scripts for each kind object (tables,
sp) and then PASTE into QA window and run them.
-Create the intended scripts and create the tables
-Transfer all the data(it's causing errors because of the table dependencies
but no problem at all, retry again all those ended in error)
--
current location: alicante (es)
"ads" wrote:
> after performing export/dts from our database server to our hosting server
,
> the primary keys of each table in the destination server are lost. using t
he
> dts wizard, i use the third option (copy database objects and data) and i
did
> make sure that the copy primary and foreign keys option is on. Can anyone
> tell me how to solve the problem?
> BTW, i did experience an error during the DTS process. "SetUser permission
> denied." but still all database objects were transfered including the
> contents except the primary keys. Does it had something to do with the
> database account im using to connect to the server, which i think is limited?[/col
or]

Primary Keys - Not Replicating

It appears that when performing a push replicaton of the transactional type
that the primary keys are not being created. In table design they show up as
clustered unique indexes type = index instead of unique constraints/ type =
primary
the clustered unique indexes are really the functionally equivalent of
primary keys (with the exception that a unique index will allow a single
null).
To replicate PK's as PK's right click on publication your publication,
select properties, click on the articles tab, and in the browse button,
click the three ellipses to the right of the article. In the snapshot tab,
click Include DRI.
"scovillesm" <scovillesm@.discussions.microsoft.com> wrote in message
news:4667423F-9248-446C-8EAB-04A67AC8E78E@.microsoft.com...
> It appears that when performing a push replicaton of the transactional
type
> that the primary keys are not being created. In table design they show up
as
> clustered unique indexes type = index instead of unique constraints/ type
=
> primary