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.
> > >
> > >
> > >
>
>
Showing posts with label weekend. Show all posts
Showing posts with label weekend. Show all posts
Wednesday, March 28, 2012
Migrating back to SQL 7 from 2000. Possible ? Advisable ? using DT
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-Copy Objects
Do you have an 'old' SQL Server7 backup files? I mean just RESTORE those
backup files to SQL Server 7 and SQL Server2000 out
"kunalap" <kunalap@.discussions.microsoft.com> wrote in message
news:E9CE8FDB-D05C-4E40-9B43-ED433F74B1DA@.microsoft.com...
> 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.
>|||Thanks for the reply.
No, I cannot restore the backups of 7 taken prior to migrating to SQL 2000
bacause there will be some transaction/activity in the database on SQL 2000
itself.
Example...they might use SQL 2000 for a week or 2 before they tell me now
they wanna go back to SQL 7 so data loss of those 2 weeks is not acceptable.
As for DTS. Im having the problem of precision being 28 on SQL 7 but 38 on
SQL 2000.
Any thoughts/suggestions ?
Thanks.
"Uri Dimant" wrote:
> DTS-Copy Objects
> Do you have an 'old' SQL Server7 backup files? I mean just RESTORE those
> backup files to SQL Server 7 and SQL Server2000 out
> "kunalap" <kunalap@.discussions.microsoft.com> wrote in message
> news:E9CE8FDB-D05C-4E40-9B43-ED433F74B1DA@.microsoft.com...
> > 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.
> >
>
>|||I see, have you tried to change (play around) with a precision?
"kunalap" <kunalap@.discussions.microsoft.com> wrote in message
news:767C75B1-9C9F-44A1-8EE2-09FDE29C16C2@.microsoft.com...
> Thanks for the reply.
> No, I cannot restore the backups of 7 taken prior to migrating to SQL 2000
> bacause there will be some transaction/activity in the database on SQL
2000
> itself.
> Example...they might use SQL 2000 for a week or 2 before they tell me now
> they wanna go back to SQL 7 so data loss of those 2 weeks is not
acceptable.
> As for DTS. Im having the problem of precision being 28 on SQL 7 but 38 on
> SQL 2000.
> Any thoughts/suggestions ?
> Thanks.
> "Uri Dimant" wrote:
> > DTS-Copy Objects
> >
> > Do you have an 'old' SQL Server7 backup files? I mean just RESTORE those
> > backup files to SQL Server 7 and SQL Server2000 out
> >
> > "kunalap" <kunalap@.discussions.microsoft.com> wrote in message
> > news:E9CE8FDB-D05C-4E40-9B43-ED433F74B1DA@.microsoft.com...
> > > 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.
> > >
> >
> >
> >|||Hi
If the business needs a plan to revert back to an old platform 2 weeks
later, then tell the business now they should do better testing before you go
live.
Once you do the migration, and run initial tests, I would say that is the
point of non-return.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"kunalap" wrote:
> Thanks for the reply.
> No, I cannot restore the backups of 7 taken prior to migrating to SQL 2000
> bacause there will be some transaction/activity in the database on SQL 2000
> itself.
> Example...they might use SQL 2000 for a week or 2 before they tell me now
> they wanna go back to SQL 7 so data loss of those 2 weeks is not acceptable.
> As for DTS. Im having the problem of precision being 28 on SQL 7 but 38 on
> SQL 2000.
> Any thoughts/suggestions ?
> Thanks.
> "Uri Dimant" wrote:
> > DTS-Copy Objects
> >
> > Do you have an 'old' SQL Server7 backup files? I mean just RESTORE those
> > backup files to SQL Server 7 and SQL Server2000 out
> >
> > "kunalap" <kunalap@.discussions.microsoft.com> wrote in message
> > news:E9CE8FDB-D05C-4E40-9B43-ED433F74B1DA@.microsoft.com...
> > > 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.
> > >
> >
> >
> >|||Thats what I have told them.
Just what I wanted to hear.
Thanks.
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> If the business needs a plan to revert back to an old platform 2 weeks
> later, then tell the business now they should do better testing before you go
> live.
> Once you do the migration, and run initial tests, I would say that is the
> point of non-return.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
>
> "kunalap" wrote:
> > Thanks for the reply.
> >
> > No, I cannot restore the backups of 7 taken prior to migrating to SQL 2000
> > bacause there will be some transaction/activity in the database on SQL 2000
> > itself.
> >
> > Example...they might use SQL 2000 for a week or 2 before they tell me now
> > they wanna go back to SQL 7 so data loss of those 2 weeks is not acceptable.
> >
> > As for DTS. Im having the problem of precision being 28 on SQL 7 but 38 on
> > SQL 2000.
> >
> > Any thoughts/suggestions ?
> >
> > Thanks.
> >
> > "Uri Dimant" wrote:
> >
> > > DTS-Copy Objects
> > >
> > > Do you have an 'old' SQL Server7 backup files? I mean just RESTORE those
> > > backup files to SQL Server 7 and SQL Server2000 out
> > >
> > > "kunalap" <kunalap@.discussions.microsoft.com> wrote in message
> > > news:E9CE8FDB-D05C-4E40-9B43-ED433F74B1DA@.microsoft.com...
> > > > 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.
> > > >
> > >
> > >
> > >
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-Copy Objects
Do you have an 'old' SQL Server7 backup files? I mean just RESTORE those
backup files to SQL Server 7 and SQL Server2000 out
"kunalap" <kunalap@.discussions.microsoft.com> wrote in message
news:E9CE8FDB-D05C-4E40-9B43-ED433F74B1DA@.microsoft.com...
> 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.
>|||Thanks for the reply.
No, I cannot restore the backups of 7 taken prior to migrating to SQL 2000
bacause there will be some transaction/activity in the database on SQL 2000
itself.
Example...they might use SQL 2000 for a week or 2 before they tell me now
they wanna go back to SQL 7 so data loss of those 2 weeks is not acceptable.
As for DTS. Im having the problem of precision being 28 on SQL 7 but 38 on
SQL 2000.
Any thoughts/suggestions ?
Thanks.
"Uri Dimant" wrote:
> DTS-Copy Objects
> Do you have an 'old' SQL Server7 backup files? I mean just RESTORE those
> backup files to SQL Server 7 and SQL Server2000 out
> "kunalap" <kunalap@.discussions.microsoft.com> wrote in message
> news:E9CE8FDB-D05C-4E40-9B43-ED433F74B1DA@.microsoft.com...
> > 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.
> >
>
>|||I see, have you tried to change (play around) with a precision?
"kunalap" <kunalap@.discussions.microsoft.com> wrote in message
news:767C75B1-9C9F-44A1-8EE2-09FDE29C16C2@.microsoft.com...
> Thanks for the reply.
> No, I cannot restore the backups of 7 taken prior to migrating to SQL 2000
> bacause there will be some transaction/activity in the database on SQL
2000
> itself.
> Example...they might use SQL 2000 for a week or 2 before they tell me now
> they wanna go back to SQL 7 so data loss of those 2 weeks is not
acceptable.
> As for DTS. Im having the problem of precision being 28 on SQL 7 but 38 on
> SQL 2000.
> Any thoughts/suggestions ?
> Thanks.
> "Uri Dimant" wrote:
> > DTS-Copy Objects
> >
> > Do you have an 'old' SQL Server7 backup files? I mean just RESTORE those
> > backup files to SQL Server 7 and SQL Server2000 out
> >
> > "kunalap" <kunalap@.discussions.microsoft.com> wrote in message
> > news:E9CE8FDB-D05C-4E40-9B43-ED433F74B1DA@.microsoft.com...
> > > 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.
> > >
> >
> >
> >|||Hi
If the business needs a plan to revert back to an old platform 2 weeks
later, then tell the business now they should do better testing before you go
live.
Once you do the migration, and run initial tests, I would say that is the
point of non-return.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"kunalap" wrote:
> Thanks for the reply.
> No, I cannot restore the backups of 7 taken prior to migrating to SQL 2000
> bacause there will be some transaction/activity in the database on SQL 2000
> itself.
> Example...they might use SQL 2000 for a week or 2 before they tell me now
> they wanna go back to SQL 7 so data loss of those 2 weeks is not acceptable.
> As for DTS. Im having the problem of precision being 28 on SQL 7 but 38 on
> SQL 2000.
> Any thoughts/suggestions ?
> Thanks.
> "Uri Dimant" wrote:
> > DTS-Copy Objects
> >
> > Do you have an 'old' SQL Server7 backup files? I mean just RESTORE those
> > backup files to SQL Server 7 and SQL Server2000 out
> >
> > "kunalap" <kunalap@.discussions.microsoft.com> wrote in message
> > news:E9CE8FDB-D05C-4E40-9B43-ED433F74B1DA@.microsoft.com...
> > > 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.
> > >
> >
> >
> >|||Thats what I have told them.
Just what I wanted to hear.
Thanks.
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> If the business needs a plan to revert back to an old platform 2 weeks
> later, then tell the business now they should do better testing before you go
> live.
> Once you do the migration, and run initial tests, I would say that is the
> point of non-return.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
>
> "kunalap" wrote:
> > Thanks for the reply.
> >
> > No, I cannot restore the backups of 7 taken prior to migrating to SQL 2000
> > bacause there will be some transaction/activity in the database on SQL 2000
> > itself.
> >
> > Example...they might use SQL 2000 for a week or 2 before they tell me now
> > they wanna go back to SQL 7 so data loss of those 2 weeks is not acceptable.
> >
> > As for DTS. Im having the problem of precision being 28 on SQL 7 but 38 on
> > SQL 2000.
> >
> > Any thoughts/suggestions ?
> >
> > Thanks.
> >
> > "Uri Dimant" wrote:
> >
> > > DTS-Copy Objects
> > >
> > > Do you have an 'old' SQL Server7 backup files? I mean just RESTORE those
> > > backup files to SQL Server 7 and SQL Server2000 out
> > >
> > > "kunalap" <kunalap@.discussions.microsoft.com> wrote in message
> > > news:E9CE8FDB-D05C-4E40-9B43-ED433F74B1DA@.microsoft.com...
> > > > 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.
> > > >
> > >
> > >
> > >
Wednesday, March 7, 2012
Microsoft Visual Studio is unable to load this document after SQL Server SP2 install.
Hello all,
Over the weekend, I loaded the SQL Server SP2 on to my production database after having it on my dev server for two weeks with out any problems.
After I did this, I went to check all my SSIS packages and found them not able to load.
I get this message “Microsoft Visual Studio is unable to load this document: The package failed to load due to error 0xC0010014 “One or more error occurred. There should be more specific errors preceding this one that explains the details of the errors. This message is used as a return value from functions that encounter errors”. This occurs when CPackage::LoadFromXML fails.
Now when I look at the errors I see:
Error 1 Error loading Master_Full_Weekly.dtsx: Error loading value "<DTS:LogProvider xmlns : DTS="www.microsoft.com/SqlServer/Dts" > <DTS : Property DTS:Name="ConfigString">SQL_TPMTSH_Datamart</DTS: Property><DTS : Property DTS:Name="DelayValidation">0</DTS: Property><DTS: Property DTS:Name="ObjectName">DTS Log Provider for SQL Serve" from node "DTS: LogProvider". D:\ETL\Projects\TPM\TPMTSH\Master_Full_Weekly.dtsx 1 1
Does anyone know what this is about and how I can go about fixing it?Anyone?|||
Could you try to register xml modules:
regsvr32 msxml3.dll
regsvr32 msxml6.dll
HTH.
Subscribe to:
Posts (Atom)