migrating DTS TO SSIS

Hi ,

Getting error even remove Text (Source) task in DTS.

Pl. help me .

Thanks,

Raja

Error:

LogID=23
#Time=11:32 AM
#Level=DTSMW_LOGLEVEL_ERR
#Source=Microsoft.SqlServer.Dts.MigrationWizard.Framework.Framework
#Message=Microsoft.SqlServer.Dts.Runtime.DtsRuntimeException: Failed to save package file "C:\PONE_SSIS_PACKAGES\PONE_SSIS_SELLTHRU\PONE_DTS_SELLTHRU_TEST.dtsx" with error 0x80004005 "Unspecified error".
> System.Runtime.InteropServices.COMException (0xC001100E): Failed to save package file "C:\PONE_SSIS_PACKAGES\PONE_SSIS_SELLTHRU\PONE_DTS_SELLTHRU_TEST.dtsx" with error 0x80004005 "Unspecified error".

at Microsoft.SqlServer.Dts.Runtime.Wrapper.ApplicationClass.SaveToXML(String FileName, IDTSPersist90 pPersistObj, IDTSEvents90 pEvents)
at Microsoft.SqlServer.Dts.Runtime.Application.SaveToXml(String fileName, Package package, IDTSEvents events)
End of inner exception stack trace
at Microsoft.SqlServer.Dts.Runtime.Application.SaveToXml(String fileName, Package package, IDTSEvents events)
at Microsoft.SqlServer.Dts.MigrationWizard.DTS9HelperUtility.DTS9Helper.SaveToXML(Package pkg, String sFileLocation)
at Microsoft.SqlServer.Dts.MigrationWizard.Framework.Framework.StartMigration(PackageInfo pInfo)

Hello Raja,

I cannot help you with your specific issue but I recomend that you do not use the DTS SSIS migration wizard. I have tried it several times but it ended with creating new SSIS packages from scratch...

/Erik
|||

Here are some other resources taht talk about DTS-SSIS migration:

http://www.google.com/search?hl=en&q=dts+to+ssis+migration

http://forums.microsoft.com/MSDN/Search/Search.aspx?words=DTS+migration&localechoice=9&SiteID=1&searchscope=forumscope&ForumID=80

|||

Hi Raja,

Did you get it fixed ? I have the similar issue scratching my head arround for several hrs.

Regards,

Rahim.

|||

Hi Rahim,

I started new SSIS and copy and paste to create second SSIS. It is easy way to start than DTS to SSIS migration. I don't find any DTS to SSIS conversion with out error.

Regards,

Raja

|||

we found that embedding legacy DTS packages in SSIS worked fine. Just create a new package and add an "Execute DTS 2000 Package Task". You can then load the old package in and embed it permenantly. We've had no problems running our old packages in this way Going forward we will rewrite as and when required.

Good luck.

|||

Hi Jez,

Thanks a lot for your response. I did as you suggested and it worked.

Regards,

Rahim

|||

Hi Raja,

Greetings!
Thank you for your response. Since we have many packages and some of them are big we couldn't copy and paste it.

Instead we created new SSIS package and then added the problem packages as DTS 2000 tasks.

Regards,

Rahim.

migrating DTS TO SSIS

Hi ,

Getting error even remove Text (Source) task in DTS.

Pl. help me .

Thanks,

Raja

Error:

LogID=23
#Time=11:32 AM
#Level=DTSMW_LOGLEVEL_ERR
#Source=Microsoft.SqlServer.Dts.MigrationWizard.Framework.Framework
#Message=Microsoft.SqlServer.Dts.Runtime.DtsRuntimeException: Failed to save package file "C:\PONE_SSIS_PACKAGES\PONE_SSIS_SELLTHRU\PONE_DTS_SELLTHRU_TEST.dtsx" with error 0x80004005 "Unspecified error".
> System.Runtime.InteropServices.COMException (0xC001100E): Failed to save package file "C:\PONE_SSIS_PACKAGES\PONE_SSIS_SELLTHRU\PONE_DTS_SELLTHRU_TEST.dtsx" with error 0x80004005 "Unspecified error".

at Microsoft.SqlServer.Dts.Runtime.Wrapper.ApplicationClass.SaveToXML(String FileName, IDTSPersist90 pPersistObj, IDTSEvents90 pEvents)
at Microsoft.SqlServer.Dts.Runtime.Application.SaveToXml(String fileName, Package package, IDTSEvents events)
End of inner exception stack trace
at Microsoft.SqlServer.Dts.Runtime.Application.SaveToXml(String fileName, Package package, IDTSEvents events)
at Microsoft.SqlServer.Dts.MigrationWizard.DTS9HelperUtility.DTS9Helper.SaveToXML(Package pkg, String sFileLocation)
at Microsoft.SqlServer.Dts.MigrationWizard.Framework.Framework.StartMigration(PackageInfo pInfo)

Hello Raja,

I cannot help you with your specific issue but I recomend that you do not use the DTS SSIS migration wizard. I have tried it several times but it ended with creating new SSIS packages from scratch...

/Erik
|||

Here are some other resources taht talk about DTS-SSIS migration:

http://www.google.com/search?hl=en&q=dts+to+ssis+migration

http://forums.microsoft.com/MSDN/Search/Search.aspx?words=DTS+migration&localechoice=9&SiteID=1&searchscope=forumscope&ForumID=80

|||

Hi Raja,

Did you get it fixed ? I have the similar issue scratching my head arround for several hrs.

Regards,

Rahim.

|||

Hi Rahim,

I started new SSIS and copy and paste to create second SSIS. It is easy way to start than DTS to SSIS migration. I don't find any DTS to SSIS conversion with out error.

Regards,

Raja

|||

we found that embedding legacy DTS packages in SSIS worked fine. Just create a new package and add an "Execute DTS 2000 Package Task". You can then load the old package in and embed it permenantly. We've had no problems running our old packages in this way Going forward we will rewrite as and when required.

Good luck.

|||

Hi Jez,

Thanks a lot for your response. I did as you suggested and it worked.

Regards,

Rahim

|||

Hi Raja,

Greetings!
Thank you for your response. Since we have many packages and some of them are big we couldn't copy and paste it.

Instead we created new SSIS package and then added the problem packages as DTS 2000 tasks.

Regards,

Rahim.

migrating DTS TO SSIS

Hi ,

Getting error even remove Text (Source) task in DTS.

Pl. help me .

Thanks,

Raja

Error:

LogID=23
#Time=11:32 AM
#Level=DTSMW_LOGLEVEL_ERR
#Source=Microsoft.SqlServer.Dts.MigrationWizard.Framework.Framework
#Message=Microsoft.SqlServer.Dts.Runtime.DtsRuntimeException: Failed to save package file "C:\PONE_SSIS_PACKAGES\PONE_SSIS_SELLTHRU\PONE_DTS_SELLTHRU_TEST.dtsx" with error 0x80004005 "Unspecified error".
> System.Runtime.InteropServices.COMException (0xC001100E): Failed to save package file "C:\PONE_SSIS_PACKAGES\PONE_SSIS_SELLTHRU\PONE_DTS_SELLTHRU_TEST.dtsx" with error 0x80004005 "Unspecified error".

at Microsoft.SqlServer.Dts.Runtime.Wrapper.ApplicationClass.SaveToXML(String FileName, IDTSPersist90 pPersistObj, IDTSEvents90 pEvents)
at Microsoft.SqlServer.Dts.Runtime.Application.SaveToXml(String fileName, Package package, IDTSEvents events)
End of inner exception stack trace
at Microsoft.SqlServer.Dts.Runtime.Application.SaveToXml(String fileName, Package package, IDTSEvents events)
at Microsoft.SqlServer.Dts.MigrationWizard.DTS9HelperUtility.DTS9Helper.SaveToXML(Package pkg, String sFileLocation)
at Microsoft.SqlServer.Dts.MigrationWizard.Framework.Framework.StartMigration(PackageInfo pInfo)

Hello Raja,

I cannot help you with your specific issue but I recomend that you do not use the DTS SSIS migration wizard. I have tried it several times but it ended with creating new SSIS packages from scratch...

/Erik
|||

Here are some other resources taht talk about DTS-SSIS migration:

http://www.google.com/search?hl=en&q=dts+to+ssis+migration

http://forums.microsoft.com/MSDN/Search/Search.aspx?words=DTS+migration&localechoice=9&SiteID=1&searchscope=forumscope&ForumID=80

|||

Hi Raja,

Did you get it fixed ? I have the similar issue scratching my head arround for several hrs.

Regards,

Rahim.

|||

Hi Rahim,

I started new SSIS and copy and paste to create second SSIS. It is easy way to start than DTS to SSIS migration. I don't find any DTS to SSIS conversion with out error.

Regards,

Raja

|||

we found that embedding legacy DTS packages in SSIS worked fine. Just create a new package and add an "Execute DTS 2000 Package Task". You can then load the old package in and embed it permenantly. We've had no problems running our old packages in this way Going forward we will rewrite as and when required.

Good luck.

|||

Hi Jez,

Thanks a lot for your response. I did as you suggested and it worked.

Regards,

Rahim

|||

Hi Raja,

Greetings!
Thank you for your response. Since we have many packages and some of them are big we couldn't copy and paste it.

Instead we created new SSIS package and then added the problem packages as DTS 2000 tasks.

Regards,

Rahim.

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:
[vbcol=seagreen]
> 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:
|||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...[vbcol=seagreen]
> 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:
|||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...
>
>
|||did you use the bakup technique (the one that i posted earlier) here?
thanks and regards
Chandra
"kunalap" wrote:
[vbcol=seagreen]
> 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:
|||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...[vbcol=seagreen]
> 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 Smeyer" wrote:
in[vbcol=seagreen]
the[vbcol=seagreen]
asked[vbcol=seagreen]
using[vbcol=seagreen]
it[vbcol=seagreen]
of[vbcol=seagreen]
2000[vbcol=seagreen]
going[vbcol=seagreen]
|||Chandra,
SQL 2000 backup cannot be applied on SQL 7.
Hence the whole DTS approach.
"Chandra" wrote:
[vbcol=seagreen]
> did you use the bakup technique (the one that i posted earlier) here?
> thanks and regards
> Chandra
>
> "kunalap" wrote:
|||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...
> in
> the
> asked
> using
> it
> of
> 2000
> going
>
>
sql

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.
> > >
> > >
> > >
>
>

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 t
o
> do this ?
> I have tried DTS from SQL 2000 to SQL 7... out of the 6 databases it worke
d
> 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:
[vbcol=seagreen]
> The best way as per me is to take a backup of your SQL 7 and restore in yo
ur
> 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:
>|||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...[vbcol=seagreen]
> 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:
>|||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...
>
>|||did you use the bakup technique (the one that i posted earlier) here?
thanks and regards
Chandra
"kunalap" wrote:
[vbcol=seagreen]
> 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:
>|||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...[vbcol=seagreen]
> 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 Smeyer" wrote:
>
in[vbcol=seagreen]
the[vbcol=seagreen]
asked[vbcol=seagreen]
using[vbcol=seagreen]
it[vbcol=seagreen]
of[vbcol=seagreen]
2000[vbcol=seagreen]
going[vbcol=seagreen]|||Chandra,
SQL 2000 backup cannot be applied on SQL 7.
Hence the whole DTS approach.
"Chandra" wrote:
[vbcol=seagreen]
> did you use the bakup technique (the one that i posted earlier) here?
> thanks and regards
> Chandra
>
> "kunalap" wrote:
>|||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 numeri
c
> 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...
> in
> the
> asked
> using
> it
> of
> 2000
> going
>
>

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.
>

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.
> > > >
> > >
> > >
> > >

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.
>

Microsoft SQL server Virtual Backup specification

Hi,
My task is to freeze SQL server so that it can be in a consistent state and after my job is done i need to thaw it. I have gone through the VDI specification given by Microsoft SQl server. It is concerned with APIs to third party vendors to take backup of SQL server with or without snapshot. Using that is there a way to do my task ?

Thanks in Advance

Can you tell us a little more about what you're trying to accomplish?

Are you building your own backup app, or what are you accomplishing by freezing the database?

There may be other less disruptive (and easier) methods to use, depending on what you're needing to do.

|||Hi Kevin,
Thanks for the reply.I want to build a backup application. But according to my requirements, i cant install VSS agent on the machine. Is there any way to freeze the SQL server using VDI ?

Microsoft SQL server Virtual Backup specification

Hi,
My task is to freeze SQL server so that it can be in a consistent state and after my job is done i need to thaw it. I have gone through the VDI specification given by Microsoft SQl server. It is concerned with APIs to third party vendors to take backup of SQL server with or without snapshot. Using that is there a way to do my task ?

Thanks in Advance

Can you tell us a little more about what you're trying to accomplish?

Are you building your own backup app, or what are you accomplishing by freezing the database?

There may be other less disruptive (and easier) methods to use, depending on what you're needing to do.

|||Hi Kevin,
Thanks for the reply.I want to build a backup application. But according to my requirements, i cant install VSS agent on the machine. Is there any way to freeze the SQL server using VDI ?

Microsoft SQL server Virtual Backup specification

Hi,
My task is to freeze SQL server so that it can be in a consistent state and after my job is done i need to thaw it. I have gone through the VDI specification given by Microsoft SQl server. It is concerned with APIs to third party vendors to take backup of SQL server with or without snapshot. Using that is there a way to do my task ?

Thanks in Advance

Can you tell us a little more about what you're trying to accomplish?

Are you building your own backup app, or what are you accomplishing by freezing the database?

There may be other less disruptive (and easier) methods to use, depending on what you're needing to do.

|||Hi Kevin,
Thanks for the reply.I want to build a backup application. But according to my requirements, i cant install VSS agent on the machine. Is there any way to freeze the SQL server using VDI ?