Wednesday, March 28, 2012

Migrating data from SQL 7 to 2000 ? Possible ? DTS ?

Hello,
I have a weird task. After going to SQL 2000 from SQL 7 on a
weekend...after a few days...incase of problems... I might be asked to
revert back to SQL 7 with those upgrade SQL 2000 databases.
Now, I know this cannot be done, but is there a possibility of using DTS to
do this ?
I have tried DTS from SQL 2000 to SQL 7... out of the 6 databases it worked
for 4. Although it does seem kind of "unclean" way to do it.
With the 5th database, I can move everything but procedures. Some of the
procedures refer to columns in user tables which don't exist.
With the 6th database, it seems max precision is set to 38 on SQL 2000 but
only 28 on SQL 7. Which is why this one isn't working at all.
Any suggestions ? Over should I just mark this "unclean" way of going from
SQL 2000 to SQL 7 as NOT an option ?
Thanks in advance.
-Kunal.The best way as per me is to take a backup of your SQL 7 and restore in your
SQL 2000.
By doing this you will not loose and objects. DTS will not copy all the
objects and the references that are available to the TABLE.
Hope this will solve your problem
thanks and regards
Chandra
"kunalap" wrote:
> Hello,
> I have a weird task. After going to SQL 2000 from SQL 7 on a
> weekend...after a few days...incase of problems... I might be asked to
> revert back to SQL 7 with those upgrade SQL 2000 databases.
> Now, I know this cannot be done, but is there a possibility of using DTS to
> do this ?
> I have tried DTS from SQL 2000 to SQL 7... out of the 6 databases it worked
> for 4. Although it does seem kind of "unclean" way to do it.
> With the 5th database, I can move everything but procedures. Some of the
> procedures refer to columns in user tables which don't exist.
> With the 6th database, it seems max precision is set to 38 on SQL 2000 but
> only 28 on SQL 7. Which is why this one isn't working at all.
> Any suggestions ? Over should I just mark this "unclean" way of going from
> SQL 2000 to SQL 7 as NOT an option ?
> Thanks in advance.
> -Kunal.|||Im sorry I made a mistake in the title of the topic.
Its SQL 2000 to SQL 7.
The matter of the topic explains the problem correctly.
Its SQL 2000 to SQL 7 not the other way around. Any thoughts ?
Thanks.
-Kunal.
"Chandra" wrote:
> The best way as per me is to take a backup of your SQL 7 and restore in your
> SQL 2000.
> By doing this you will not loose and objects. DTS will not copy all the
> objects and the references that are available to the TABLE.
> Hope this will solve your problem
> thanks and regards
> Chandra
>
> "kunalap" wrote:
> > Hello,
> >
> > I have a weird task. After going to SQL 2000 from SQL 7 on a
> > weekend...after a few days...incase of problems... I might be asked to
> > revert back to SQL 7 with those upgrade SQL 2000 databases.
> >
> > Now, I know this cannot be done, but is there a possibility of using DTS to
> > do this ?
> > I have tried DTS from SQL 2000 to SQL 7... out of the 6 databases it worked
> > for 4. Although it does seem kind of "unclean" way to do it.
> >
> > With the 5th database, I can move everything but procedures. Some of the
> > procedures refer to columns in user tables which don't exist.
> >
> > With the 6th database, it seems max precision is set to 38 on SQL 2000 but
> > only 28 on SQL 7. Which is why this one isn't working at all.
> >
> > Any suggestions ? Over should I just mark this "unclean" way of going from
> > SQL 2000 to SQL 7 as NOT an option ?
> >
> > Thanks in advance.
> >
> > -Kunal.|||DTS the objects from the 2000 to the 7.0 server.
HTH, Jens Suessmeyer.
--
http://www.sqlserver2005.de
--
"kunalap" <kunalap@.discussions.microsoft.com> schrieb im Newsbeitrag
news:7A7185B2-8DDC-4FB7-929A-F32AB5D5703E@.microsoft.com...
> Im sorry I made a mistake in the title of the topic.
> Its SQL 2000 to SQL 7.
> The matter of the topic explains the problem correctly.
> Its SQL 2000 to SQL 7 not the other way around. Any thoughts ?
> Thanks.
> -Kunal.
> "Chandra" wrote:
>> The best way as per me is to take a backup of your SQL 7 and restore in
>> your
>> SQL 2000.
>> By doing this you will not loose and objects. DTS will not copy all the
>> objects and the references that are available to the TABLE.
>> Hope this will solve your problem
>> thanks and regards
>> Chandra
>>
>> "kunalap" wrote:
>> > Hello,
>> >
>> > I have a weird task. After going to SQL 2000 from SQL 7 on a
>> > weekend...after a few days...incase of problems... I might be asked
>> > to
>> > revert back to SQL 7 with those upgrade SQL 2000 databases.
>> >
>> > Now, I know this cannot be done, but is there a possibility of using
>> > DTS to
>> > do this ?
>> > I have tried DTS from SQL 2000 to SQL 7... out of the 6 databases it
>> > worked
>> > for 4. Although it does seem kind of "unclean" way to do it.
>> >
>> > With the 5th database, I can move everything but procedures. Some of
>> > the
>> > procedures refer to columns in user tables which don't exist.
>> >
>> > With the 6th database, it seems max precision is set to 38 on SQL 2000
>> > but
>> > only 28 on SQL 7. Which is why this one isn't working at all.
>> >
>> > Any suggestions ? Over should I just mark this "unclean" way of going
>> > from
>> > SQL 2000 to SQL 7 as NOT an option ?
>> >
>> > Thanks in advance.
>> >
>> > -Kunal.|||Yes thats what I am trying. But doesn't it seem kind of "unclean" way to
maintain production data. Also the 2 problems Im having with 2 of the
databases in DTS'ing.
Any advise ?
"Jens Sü�meyer" wrote:
> DTS the objects from the 2000 to the 7.0 server.
>
> HTH, Jens Suessmeyer.
> --
> http://www.sqlserver2005.de
> --
>
> "kunalap" <kunalap@.discussions.microsoft.com> schrieb im Newsbeitrag
> news:7A7185B2-8DDC-4FB7-929A-F32AB5D5703E@.microsoft.com...
> > Im sorry I made a mistake in the title of the topic.
> > Its SQL 2000 to SQL 7.
> >
> > The matter of the topic explains the problem correctly.
> >
> > Its SQL 2000 to SQL 7 not the other way around. Any thoughts ?
> >
> > Thanks.
> >
> > -Kunal.
> >
> > "Chandra" wrote:
> >
> >> The best way as per me is to take a backup of your SQL 7 and restore in
> >> your
> >> SQL 2000.
> >>
> >> By doing this you will not loose and objects. DTS will not copy all the
> >> objects and the references that are available to the TABLE.
> >>
> >> Hope this will solve your problem
> >>
> >> thanks and regards
> >> Chandra
> >>
> >>
> >> "kunalap" wrote:
> >>
> >> > Hello,
> >> >
> >> > I have a weird task. After going to SQL 2000 from SQL 7 on a
> >> > weekend...after a few days...incase of problems... I might be asked
> >> > to
> >> > revert back to SQL 7 with those upgrade SQL 2000 databases.
> >> >
> >> > Now, I know this cannot be done, but is there a possibility of using
> >> > DTS to
> >> > do this ?
> >> > I have tried DTS from SQL 2000 to SQL 7... out of the 6 databases it
> >> > worked
> >> > for 4. Although it does seem kind of "unclean" way to do it.
> >> >
> >> > With the 5th database, I can move everything but procedures. Some of
> >> > the
> >> > procedures refer to columns in user tables which don't exist.
> >> >
> >> > With the 6th database, it seems max precision is set to 38 on SQL 2000
> >> > but
> >> > only 28 on SQL 7. Which is why this one isn't working at all.
> >> >
> >> > Any suggestions ? Over should I just mark this "unclean" way of going
> >> > from
> >> > SQL 2000 to SQL 7 as NOT an option ?
> >> >
> >> > Thanks in advance.
> >> >
> >> > -Kunal.
>
>|||did you use the bakup technique (the one that i posted earlier) here?
thanks and regards
Chandra
"kunalap" wrote:
> Yes thats what I am trying. But doesn't it seem kind of "unclean" way to
> maintain production data. Also the 2 problems Im having with 2 of the
> databases in DTS'ing.
> Any advise ?
> "Jens Sü�meyer" wrote:
> > DTS the objects from the 2000 to the 7.0 server.
> >
> >
> > HTH, Jens Suessmeyer.
> >
> > --
> > http://www.sqlserver2005.de
> > --
> >
> >
> >
> > "kunalap" <kunalap@.discussions.microsoft.com> schrieb im Newsbeitrag
> > news:7A7185B2-8DDC-4FB7-929A-F32AB5D5703E@.microsoft.com...
> > > Im sorry I made a mistake in the title of the topic.
> > > Its SQL 2000 to SQL 7.
> > >
> > > The matter of the topic explains the problem correctly.
> > >
> > > Its SQL 2000 to SQL 7 not the other way around. Any thoughts ?
> > >
> > > Thanks.
> > >
> > > -Kunal.
> > >
> > > "Chandra" wrote:
> > >
> > >> The best way as per me is to take a backup of your SQL 7 and restore in
> > >> your
> > >> SQL 2000.
> > >>
> > >> By doing this you will not loose and objects. DTS will not copy all the
> > >> objects and the references that are available to the TABLE.
> > >>
> > >> Hope this will solve your problem
> > >>
> > >> thanks and regards
> > >> Chandra
> > >>
> > >>
> > >> "kunalap" wrote:
> > >>
> > >> > Hello,
> > >> >
> > >> > I have a weird task. After going to SQL 2000 from SQL 7 on a
> > >> > weekend...after a few days...incase of problems... I might be asked
> > >> > to
> > >> > revert back to SQL 7 with those upgrade SQL 2000 databases.
> > >> >
> > >> > Now, I know this cannot be done, but is there a possibility of using
> > >> > DTS to
> > >> > do this ?
> > >> > I have tried DTS from SQL 2000 to SQL 7... out of the 6 databases it
> > >> > worked
> > >> > for 4. Although it does seem kind of "unclean" way to do it.
> > >> >
> > >> > With the 5th database, I can move everything but procedures. Some of
> > >> > the
> > >> > procedures refer to columns in user tables which don't exist.
> > >> >
> > >> > With the 6th database, it seems max precision is set to 38 on SQL 2000
> > >> > but
> > >> > only 28 on SQL 7. Which is why this one isn't working at all.
> > >> >
> > >> > Any suggestions ? Over should I just mark this "unclean" way of going
> > >> > from
> > >> > SQL 2000 to SQL 7 as NOT an option ?
> > >> >
> > >> > Thanks in advance.
> > >> >
> > >> > -Kunal.
> >
> >
> >|||Transfer whatewer possible with DTS, and then:
1. Try to script objects (procedures etc.) on 7.0 and run the script on
2000.
2. Check options when transferring - allow demotion (shrink) of the numeric
data types.
--
Dejan Sarka, SQL Server MVP
Associate Mentor
www.SolidQualityLearning.com
"kunalap" <kunalap@.discussions.microsoft.com> wrote in message
news:F788F92D-7DE0-44BF-9578-6A4F51C7E9DC@.microsoft.com...
> Yes thats what I am trying. But doesn't it seem kind of "unclean" way to
> maintain production data. Also the 2 problems Im having with 2 of the
> databases in DTS'ing.
> Any advise ?
> "Jens Süßmeyer" wrote:
> > DTS the objects from the 2000 to the 7.0 server.
> >
> >
> > HTH, Jens Suessmeyer.
> >
> > --
> > http://www.sqlserver2005.de
> > --
> >
> >
> >
> > "kunalap" <kunalap@.discussions.microsoft.com> schrieb im Newsbeitrag
> > news:7A7185B2-8DDC-4FB7-929A-F32AB5D5703E@.microsoft.com...
> > > Im sorry I made a mistake in the title of the topic.
> > > Its SQL 2000 to SQL 7.
> > >
> > > The matter of the topic explains the problem correctly.
> > >
> > > Its SQL 2000 to SQL 7 not the other way around. Any thoughts ?
> > >
> > > Thanks.
> > >
> > > -Kunal.
> > >
> > > "Chandra" wrote:
> > >
> > >> The best way as per me is to take a backup of your SQL 7 and restore
in
> > >> your
> > >> SQL 2000.
> > >>
> > >> By doing this you will not loose and objects. DTS will not copy all
the
> > >> objects and the references that are available to the TABLE.
> > >>
> > >> Hope this will solve your problem
> > >>
> > >> thanks and regards
> > >> Chandra
> > >>
> > >>
> > >> "kunalap" wrote:
> > >>
> > >> > Hello,
> > >> >
> > >> > I have a weird task. After going to SQL 2000 from SQL 7 on a
> > >> > weekend...after a few days...incase of problems... I might be
asked
> > >> > to
> > >> > revert back to SQL 7 with those upgrade SQL 2000 databases.
> > >> >
> > >> > Now, I know this cannot be done, but is there a possibility of
using
> > >> > DTS to
> > >> > do this ?
> > >> > I have tried DTS from SQL 2000 to SQL 7... out of the 6 databases
it
> > >> > worked
> > >> > for 4. Although it does seem kind of "unclean" way to do it.
> > >> >
> > >> > With the 5th database, I can move everything but procedures. Some
of
> > >> > the
> > >> > procedures refer to columns in user tables which don't exist.
> > >> >
> > >> > With the 6th database, it seems max precision is set to 38 on SQL
2000
> > >> > but
> > >> > only 28 on SQL 7. Which is why this one isn't working at all.
> > >> >
> > >> > Any suggestions ? Over should I just mark this "unclean" way of
going
> > >> > from
> > >> > SQL 2000 to SQL 7 as NOT an option ?
> > >> >
> > >> > Thanks in advance.
> > >> >
> > >> > -Kunal.
> >
> >
> >|||Chandra,
SQL 2000 backup cannot be applied on SQL 7.
Hence the whole DTS approach.
"Chandra" wrote:
> did you use the bakup technique (the one that i posted earlier) here?
> thanks and regards
> Chandra
>
> "kunalap" wrote:
> > Yes thats what I am trying. But doesn't it seem kind of "unclean" way to
> > maintain production data. Also the 2 problems Im having with 2 of the
> > databases in DTS'ing.
> >
> > Any advise ?
> >
> > "Jens Sü�meyer" wrote:
> >
> > > DTS the objects from the 2000 to the 7.0 server.
> > >
> > >
> > > HTH, Jens Suessmeyer.
> > >
> > > --
> > > http://www.sqlserver2005.de
> > > --
> > >
> > >
> > >
> > > "kunalap" <kunalap@.discussions.microsoft.com> schrieb im Newsbeitrag
> > > news:7A7185B2-8DDC-4FB7-929A-F32AB5D5703E@.microsoft.com...
> > > > Im sorry I made a mistake in the title of the topic.
> > > > Its SQL 2000 to SQL 7.
> > > >
> > > > The matter of the topic explains the problem correctly.
> > > >
> > > > Its SQL 2000 to SQL 7 not the other way around. Any thoughts ?
> > > >
> > > > Thanks.
> > > >
> > > > -Kunal.
> > > >
> > > > "Chandra" wrote:
> > > >
> > > >> The best way as per me is to take a backup of your SQL 7 and restore in
> > > >> your
> > > >> SQL 2000.
> > > >>
> > > >> By doing this you will not loose and objects. DTS will not copy all the
> > > >> objects and the references that are available to the TABLE.
> > > >>
> > > >> Hope this will solve your problem
> > > >>
> > > >> thanks and regards
> > > >> Chandra
> > > >>
> > > >>
> > > >> "kunalap" wrote:
> > > >>
> > > >> > Hello,
> > > >> >
> > > >> > I have a weird task. After going to SQL 2000 from SQL 7 on a
> > > >> > weekend...after a few days...incase of problems... I might be asked
> > > >> > to
> > > >> > revert back to SQL 7 with those upgrade SQL 2000 databases.
> > > >> >
> > > >> > Now, I know this cannot be done, but is there a possibility of using
> > > >> > DTS to
> > > >> > do this ?
> > > >> > I have tried DTS from SQL 2000 to SQL 7... out of the 6 databases it
> > > >> > worked
> > > >> > for 4. Although it does seem kind of "unclean" way to do it.
> > > >> >
> > > >> > With the 5th database, I can move everything but procedures. Some of
> > > >> > the
> > > >> > procedures refer to columns in user tables which don't exist.
> > > >> >
> > > >> > With the 6th database, it seems max precision is set to 38 on SQL 2000
> > > >> > but
> > > >> > only 28 on SQL 7. Which is why this one isn't working at all.
> > > >> >
> > > >> > Any suggestions ? Over should I just mark this "unclean" way of going
> > > >> > from
> > > >> > SQL 2000 to SQL 7 as NOT an option ?
> > > >> >
> > > >> > Thanks in advance.
> > > >> >
> > > >> > -Kunal.
> > >
> > >
> > >|||You mean script out on 2000 and then apply on 7, right ? coz thats what im
trying to do. move from sql 2000 to sql 7.
And this demotion option. where is this ? I dont recall ever seeing such an
option in DTS or in script out objects.
Please let me know.
Thanks.
-Kunal.
"Dejan Sarka" wrote:
> Transfer whatewer possible with DTS, and then:
> 1. Try to script objects (procedures etc.) on 7.0 and run the script on
> 2000.
> 2. Check options when transferring - allow demotion (shrink) of the numeric
> data types.
> --
> Dejan Sarka, SQL Server MVP
> Associate Mentor
> www.SolidQualityLearning.com
> "kunalap" <kunalap@.discussions.microsoft.com> wrote in message
> news:F788F92D-7DE0-44BF-9578-6A4F51C7E9DC@.microsoft.com...
> > Yes thats what I am trying. But doesn't it seem kind of "unclean" way to
> > maintain production data. Also the 2 problems Im having with 2 of the
> > databases in DTS'ing.
> >
> > Any advise ?
> >
> > "Jens Sü�meyer" wrote:
> >
> > > DTS the objects from the 2000 to the 7.0 server.
> > >
> > >
> > > HTH, Jens Suessmeyer.
> > >
> > > --
> > > http://www.sqlserver2005.de
> > > --
> > >
> > >
> > >
> > > "kunalap" <kunalap@.discussions.microsoft.com> schrieb im Newsbeitrag
> > > news:7A7185B2-8DDC-4FB7-929A-F32AB5D5703E@.microsoft.com...
> > > > Im sorry I made a mistake in the title of the topic.
> > > > Its SQL 2000 to SQL 7.
> > > >
> > > > The matter of the topic explains the problem correctly.
> > > >
> > > > Its SQL 2000 to SQL 7 not the other way around. Any thoughts ?
> > > >
> > > > Thanks.
> > > >
> > > > -Kunal.
> > > >
> > > > "Chandra" wrote:
> > > >
> > > >> The best way as per me is to take a backup of your SQL 7 and restore
> in
> > > >> your
> > > >> SQL 2000.
> > > >>
> > > >> By doing this you will not loose and objects. DTS will not copy all
> the
> > > >> objects and the references that are available to the TABLE.
> > > >>
> > > >> Hope this will solve your problem
> > > >>
> > > >> thanks and regards
> > > >> Chandra
> > > >>
> > > >>
> > > >> "kunalap" wrote:
> > > >>
> > > >> > Hello,
> > > >> >
> > > >> > I have a weird task. After going to SQL 2000 from SQL 7 on a
> > > >> > weekend...after a few days...incase of problems... I might be
> asked
> > > >> > to
> > > >> > revert back to SQL 7 with those upgrade SQL 2000 databases.
> > > >> >
> > > >> > Now, I know this cannot be done, but is there a possibility of
> using
> > > >> > DTS to
> > > >> > do this ?
> > > >> > I have tried DTS from SQL 2000 to SQL 7... out of the 6 databases
> it
> > > >> > worked
> > > >> > for 4. Although it does seem kind of "unclean" way to do it.
> > > >> >
> > > >> > With the 5th database, I can move everything but procedures. Some
> of
> > > >> > the
> > > >> > procedures refer to columns in user tables which don't exist.
> > > >> >
> > > >> > With the 6th database, it seems max precision is set to 38 on SQL
> 2000
> > > >> > but
> > > >> > only 28 on SQL 7. Which is why this one isn't working at all.
> > > >> >
> > > >> > Any suggestions ? Over should I just mark this "unclean" way of
> going
> > > >> > from
> > > >> > SQL 2000 to SQL 7 as NOT an option ?
> > > >> >
> > > >> > Thanks in advance.
> > > >> >
> > > >> > -Kunal.
> > >
> > >
> > >
>
>

No comments:

Post a Comment