PHWinfo - Afficher un message - SQL 2000 Enterprise Edition to SQL 2005 Standard Edition

22/09/2006, 00h08

When you install EE, you are installing DLLs containing bits that provide
extra functionality. The DLLs 'may' have the same name/signature as the ones
for SD. It only makes sense that you would be required to remove all of the
EE bits in order to 'downgrade'.

--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc

Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous

"QNguyen" <QNguyen@discussions.microsoft.com> wrote in message
news:7EFC030D-31C0-4D23-AC36-CCE5E448931B@microsoft.com...
> Thanks, Arnie. That's what I thought. I was hoping there would be an
> undocumented process that would allow to go from SQL2000 Enterprise
> Edition
> => SQL2005 Standard Edition with in-place upgrade. But from the sounds of
> it, there isn't an undocumented process.
>
> "Arnie Rowland" wrote:
>
>> I believe that the only option is to uninstall EE and reinstall SD.
>>
>> You may wish to do the side-by-side in order to preserve the existing
>> structure in case anything goes wrong. Otherwise, you need to detach the
>> databases, be sure you have records of the logins, etc.
>>
>> Some of these may :
>>
>> http://www.support.microsoft.com/?id=314546 Moving DB's between Servers
>> http://www.support.microsoft.com/?id=224071 Moving SQL Server Databases
>> to a
>> New Location with Detach/Attach
>> http://www.support.microsoft.com/?id=221465 Using WITH MOVE in a Restore
>> http://www.sqlservercentral.com/colu...rdatabases.asp
>> Moving Users
>> http://www.support.microsoft.com/?id=246133 How To Transfer Logins and
>> Passwords Between SQL Servers
>> http://www.support.microsoft.com/?id=298897 Mapping Logins & SIDs after a
>> Restore
>> http://www.dbmaint.com/SyncSqlLogins.asp Utility to map logins to users
>> http://www.support.microsoft.com/?id=168001 User Logon and/or Permission
>> Errors After Restoring Dump
>> http://support.microsoft.com/kb/274188 Troubleshooting Orphan Logins
>> http://www.support.microsoft.com/?id=240872 Resolve Permission
>> Issues -Database Is Moved Between SQL Servers
>>
>>
>>
>> --
>> Arnie Rowland, Ph.D.
>> Westwood Consulting, Inc
>>
>> Most good judgment comes from experience.
>> Most experience comes from bad judgment.
>> - Anonymous
>>
>>
>> "QNguyen" <QNguyen@discussions.microsoft.com> wrote in message
>> news:3D22B46F-1BC9-402A-A0F1-BE0AA76EBA0D@microsoft.com...
>> > Does anyone have any experience with in-place upgrade of SQL 2000
>> > ENTERPRISE
>> > Edition => SQL 2005 STANDARD Edition? According to Microsoft upgrade
>> > path,
>> > it's SQL Server 2000 Enterprise Edition SP3 or later => SQL Server 2005
>> > Enterprise Edition. The only way that I can think of right now is to
>> > downgrade the SQL2000 instance to Standard. But this will require a
>> > lot
>> > of
>> > work. I want to avoid this. Also, I want to avoid doing the
>> > side-by-side
>> > upgrade, too.
>> >
>>
>>
>>

22/09/2006, 00h08	#4
Arnie Rowland Messages: n/a Hébergeur:	Re: SQL 2000 Enterprise Edition to SQL 2005 Standard Edition When you install EE, you are installing DLLs containing bits that provide extra functionality. The DLLs 'may' have the same name/signature as the ones for SD. It only makes sense that you would be required to remove all of the EE bits in order to 'downgrade'. -- Arnie Rowland, Ph.D. Westwood Consulting, Inc Most good judgment comes from experience. Most experience comes from bad judgment. - Anonymous "QNguyen" <QNguyen@discussions.microsoft.com> wrote in message news:7EFC030D-31C0-4D23-AC36-CCE5E448931B@microsoft.com... > Thanks, Arnie. That's what I thought. I was hoping there would be an > undocumented process that would allow to go from SQL2000 Enterprise > Edition > => SQL2005 Standard Edition with in-place upgrade. But from the sounds of > it, there isn't an undocumented process. > > "Arnie Rowland" wrote: > >> I believe that the only option is to uninstall EE and reinstall SD. >> >> You may wish to do the side-by-side in order to preserve the existing >> structure in case anything goes wrong. Otherwise, you need to detach the >> databases, be sure you have records of the logins, etc. >> >> Some of these may : >> >> http://www.support.microsoft.com/?id=314546 Moving DB's between Servers >> http://www.support.microsoft.com/?id=224071 Moving SQL Server Databases >> to a >> New Location with Detach/Attach >> http://www.support.microsoft.com/?id=221465 Using WITH MOVE in a Restore >> http://www.sqlservercentral.com/colu...rdatabases.asp >> Moving Users >> http://www.support.microsoft.com/?id=246133 How To Transfer Logins and >> Passwords Between SQL Servers >> http://www.support.microsoft.com/?id=298897 Mapping Logins & SIDs after a >> Restore >> http://www.dbmaint.com/SyncSqlLogins.asp Utility to map logins to users >> http://www.support.microsoft.com/?id=168001 User Logon and/or Permission >> Errors After Restoring Dump >> http://support.microsoft.com/kb/274188 Troubleshooting Orphan Logins >> http://www.support.microsoft.com/?id=240872 Resolve Permission >> Issues -Database Is Moved Between SQL Servers >> >> >> >> -- >> Arnie Rowland, Ph.D. >> Westwood Consulting, Inc >> >> Most good judgment comes from experience. >> Most experience comes from bad judgment. >> - Anonymous >> >> >> "QNguyen" <QNguyen@discussions.microsoft.com> wrote in message >> news:3D22B46F-1BC9-402A-A0F1-BE0AA76EBA0D@microsoft.com... >> > Does anyone have any experience with in-place upgrade of SQL 2000 >> > ENTERPRISE >> > Edition => SQL 2005 STANDARD Edition? According to Microsoft upgrade >> > path, >> > it's SQL Server 2000 Enterprise Edition SP3 or later => SQL Server 2005 >> > Enterprise Edition. The only way that I can think of right now is to >> > downgrade the SQL2000 instance to Standard. But this will require a >> > lot >> > of >> > work. I want to avoid this. Also, I want to avoid doing the >> > side-by-side >> > upgrade, too. >> > >> >> >>