"Richard K Bethell" <softdev@spammingisevil.bad> wrote in message
news:OP%23TK1G7FHA.1028@TK2MSFTNGP11.phx.gbl...
>I really wanted to be enthusiastic about SQL Server 2005. I'm not off to a
>great start with that. I'm stymied by yet another wizard that is anything
>but.
>
> I tried to copy a database from a 2000 server to a 2005 server using the
> new "Management Studio" - I got a cryptic message about "Integration SSIS
> proxy" accounts not existing and stuff about subsystems, so I looked
> around newsgroups, and realized that I had not installed "Integration
> Services", needed to make this happen. So I did.
>
> After installing this component, I went into the proxies, to SSIS Package
> Execution, got told I had to make a credential, which I went and did...
> then it bombed out on me with a "specified @subsystem_id (11) does not
> exist" message. When I tried again, it asserted that the proxy exists...
> but I could see no evidence of this new proxy name, nor does it show up in
> this newfangled copy wizard afterwords. I tried all this again with a new
> proxy name, this time clicking "script" instead of the "OK" button. When I
> run the script I still get the message about @subsystem_id.
>
> This is a real step down from the old DTS wizard... mainly in that I could
> get that to work without all these confusing runarounds. Is there anyone
> who can help me to get where I need to go with this? I just want to copy
> some databases... is there a simple way? Can I, if nothing else, at least
> copy and attach? At least that I can understand...
>

"Jasper Smith" <jasper_smi***@hotmail.com> wrote in message
news:OeCleBH7FHA.1140@tk2msftngp13.phx.gbl...
> I've never been a fan of the CDW in 2000 or 2005. Much simpler to
> backup/restore or detach/attach. Note that this will leave your database
> in 80 compatability mode so you'll need to run
>
> EXEC sp_dbcmptlevel 'database name', '90'
>
> --
> HTH
>
> Jasper Smith (SQL Server MVP)
> http://www.sqldbatips.com
> I support PASS - the definitive, global
> community for SQL Server professionals -
> http://www.sqlpass.org
>
> "Richard K Bethell" <softdev@spammingisevil.bad> wrote in message
> news:OP%23TK1G7FHA.1028@TK2MSFTNGP11.phx.gbl...
>>I really wanted to be enthusiastic about SQL Server 2005. I'm not off to a
>>great start with that. I'm stymied by yet another wizard that is anything
>>but.
>>
>> I tried to copy a database from a 2000 server to a 2005 server using the
>> new "Management Studio" - I got a cryptic message about "Integration SSIS
>> proxy" accounts not existing and stuff about subsystems, so I looked
>> around newsgroups, and realized that I had not installed "Integration
>> Services", needed to make this happen. So I did.
>>
>> After installing this component, I went into the proxies, to SSIS Package
>> Execution, got told I had to make a credential, which I went and did...
>> then it bombed out on me with a "specified @subsystem_id (11) does not
>> exist" message. When I tried again, it asserted that the proxy exists...
>> but I could see no evidence of this new proxy name, nor does it show up
>> in this newfangled copy wizard afterwords. I tried all this again with a
>> new proxy name, this time clicking "script" instead of the "OK" button.
>> When I run the script I still get the message about @subsystem_id.
>>
>> This is a real step down from the old DTS wizard... mainly in that I
>> could get that to work without all these confusing runarounds. Is there
>> anyone who can help me to get where I need to go with this? I just want
>> to copy some databases... is there a simple way? Can I, if nothing else,
>> at least copy and attach? At least that I can understand...
>>
>
>

"Richard K Bethell" <softdev@spammingisevil.bad> wrote in message
news:OJMDWSH7FHA.2484@TK2MSFTNGP10.phx.gbl...
> It appears to have gotten worse in 2005, even. :-) Thanks for the
> compatibility tip! I probably would have forgotten about that...
>
> "Jasper Smith" <jasper_smi***@hotmail.com> wrote in message
> news:OeCleBH7FHA.1140@tk2msftngp13.phx.gbl...
>> I've never been a fan of the CDW in 2000 or 2005. Much simpler to
>> backup/restore or detach/attach. Note that this will leave your database
>> in 80 compatability mode so you'll need to run
>>
>> EXEC sp_dbcmptlevel 'database name', '90'
>>
>> --
>> HTH
>>
>> Jasper Smith (SQL Server MVP)
>> http://www.sqldbatips.com
>> I support PASS - the definitive, global
>> community for SQL Server professionals -
>> http://www.sqlpass.org
>>
>> "Richard K Bethell" <softdev@spammingisevil.bad> wrote in message
>> news:OP%23TK1G7FHA.1028@TK2MSFTNGP11.phx.gbl...
>>>I really wanted to be enthusiastic about SQL Server 2005. I'm not off to
>>>a great start with that. I'm stymied by yet another wizard that is
>>>anything but.
>>>
>>> I tried to copy a database from a 2000 server to a 2005 server using the
>>> new "Management Studio" - I got a cryptic message about "Integration
>>> SSIS proxy" accounts not existing and stuff about subsystems, so I
>>> looked around newsgroups, and realized that I had not installed
>>> "Integration Services", needed to make this happen. So I did.
>>>
>>> After installing this component, I went into the proxies, to SSIS
>>> Package Execution, got told I had to make a credential, which I went and
>>> did... then it bombed out on me with a "specified @subsystem_id (11)
>>> does not exist" message. When I tried again, it asserted that the proxy
>>> exists... but I could see no evidence of this new proxy name, nor does
>>> it show up in this newfangled copy wizard afterwords. I tried all this
>>> again with a new proxy name, this time clicking "script" instead of the
>>> "OK" button. When I run the script I still get the message about
>>> @subsystem_id.
>>>
>>> This is a real step down from the old DTS wizard... mainly in that I
>>> could get that to work without all these confusing runarounds. Is there
>>> anyone who can help me to get where I need to go with this? I just want
>>> to copy some databases... is there a simple way? Can I, if nothing else,
>>> at least copy and attach? At least that I can understand...
>>>
>>
>>
>
>