Problems in exporting constraints and keys

From: "Chakravarthy" <r_chakravarthy@xxxxxxxxxxx>
Date: Sun, 7 Jan 2007 21:16:24 +0530

When i try to replicate a production database as a new development database
by creating an empty DB called, say 'AppDev' in Enterprise Manager, and then
export the data using the Tasks->Export Data , the constraints, Primary Keys
and Foreign Keys are not exported , even though i have selected these
options . The data however is exported.

Is there a catch, or a better way to do this ?

Thanks,
Raj.

.

Follow-Ups:
- Re: Problems in exporting constraints and keys
  - From: Andrew J. Kelly

Prev by Date: Linked Server Between two machines in different domains with different SQL versions
Next by Date: Re: Linked Server Between two machines in different domains with different SQL versions
Previous by thread: Linked Server Between two machines in different domains with different SQL versions
Next by thread: Re: Problems in exporting constraints and keys
Index(es):
- Date
- Thread

Relevant Pages

Restricted access to Enterprise manager
... I want to restrict the access to enterprise manager from the developer ... They need the access the develpment machine so they require ... the production database from their workstation enterprise manager. ...
(microsoft.public.sqlserver.clients)
Re: Restricted access to Enterprise manager
... > I want to restrict the access to enterprise manager from the developer ... They need the access the develpment machine so they require ... > the production database from their workstation enterprise manager. ...
(microsoft.public.sqlserver.clients)
Re: Enterprise Manager causes blocks?
... That's because Enterprise Manager holds locks open and Query Analyzer does ... You should not use EM on a production database. ... Arnie Rowland* ... "To be successful, your heart must accompany your knowledge." ...
(microsoft.public.sqlserver.tools)