Re: Moving Full database to Empty database
- From: "Andrew J. Kelly" <sqlmvpnooospam@xxxxxxxxxxxx>
- Date: Sat, 24 Dec 2005 15:00:24 -0500
Why do you need to create a whole new db just to upgrade it? Why not simply
alter the existing tables?
--
Andrew J. Kelly SQL MVP
"Roy Goldhammer" <roy@xxxxxxxxxxx> wrote in message
news:%23hr5HOJCGHA.3868@xxxxxxxxxxxxxxxxxxxxxxx
> Whell Andrew
>
> 3rd option is impossible, because i usually do this for upgrating vertion,
> so the schema is changed
>
> 1st option looks the most way. But can i script only the relationships or
> script droping of them?
> "Andrew J. Kelly" <sqlmvpnooospam@xxxxxxxxxxxx> wrote in message
> news:O4pknJJCGHA.1312@xxxxxxxxxxxxxxxxxxxxxxx
>> You basically have 3 options.
>>
>> 1. Drop the RI, Import the data and then recreate the RI.
>>
>> 2. Script the imports so that they follow Parent Child order.
>>
>> 3. Do a Restore of the full db over top of the Empty DB.
>>
>> I recommend the 3rd option if you want everything.
>>
>>
>> --
>> Andrew J. Kelly SQL MVP
>>
>>
>> "Roy Goldhammer" <roy@xxxxxxxxxxx> wrote in message
>> news:evVFTJICGHA.2664@xxxxxxxxxxxxxxxxxxxxxxx
>> > Hello there
>> >
>> > I have database with many relationsips
>> >
>> > At the start it is empty and when i'm trying to import to it data. some
> of
>> > the tables are failed due to key violations
>> >
>> > Is there a way to import the data in this cases?
>> >
>> >
>> >
>>
>>
>
>
.
- References:
- Moving Full database to Empty database
- From: Roy Goldhammer
- Re: Moving Full database to Empty database
- From: Andrew J. Kelly
- Re: Moving Full database to Empty database
- From: Roy Goldhammer
- Moving Full database to Empty database
- Prev by Date: Re: Log File is growing
- Next by Date: Moving Full database to Empty database
- Previous by thread: Re: Moving Full database to Empty database
- Index(es):
Relevant Pages
|
Loading