Posted by DataPro on 10/02/52 11:54

Thanks...ran a few tests looking at the dll before and after trying
different options and kept the keys. Worked out fine...makes you wonder
why Microsoft would use an example of a dts move in its book for
newbies that would only confuse the issue.


Erland Sommarskog wrote:
> DataPro (datapro01@yahoo.com) writes:
> > Very new to SQL Server. Was asked to copy some tables from a Prod to a
> > Test database in the same instance. (This system is not yet in
> > production.)
> >
> > I used the Microsoft course book guidance for course 2072 A, the lab
> > exercise in Module 9, page 33 to give me some guidance. In the exercise
> > they were copying tables as well as views.
> >
> > While in the wizard the guidance said to uncheck 'copy primary and
> > foreign keys' and uncheck 'copy full text indexes'.
> >
> > While I realize that might be because of the nature of copying views, I
> > used that guidance to copy the tables. Is this correct or should I do
> > it over and copy both the keys and full text indexes?
>
> You should certainly copy the keys. I don't use full-text, so I don't know
> if there is any good reason why they are not copied by default. Then
> again, with a little luck your database does have full-text indexes.
>
> --
> Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
>
> Books Online for SQL Server 2005 at
> http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
> Books Online for SQL Server 2000 at
> http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx

[Back to original message]