Re: How to convert the SQL Developer Edition to SQL Standard Editi

From: Andrew J. Kelly (sqlmvpnooospam_at_shadhawk.com)
Date: 01/12/05


Date: Tue, 11 Jan 2005 21:30:09 -0500

If you run the setup for the Std Edition on that machine it should guide you
through an upgrade. There should be no need to change where any of the
drivers point since the server will be the same as long as you upgrade the
existing instance and don't add a new one.

-- 
Andrew J. Kelly  SQL MVP
"Kam" <Kam@discussions.microsoft.com> wrote in message 
news:91043082-8466-4D3E-A4C6-F91B88634D9F@microsoft.com...
> Yes, you are right.
>
> When I install other microsoft product, I install the Desktop engine by
> mistake.
> Now all my Replication Database, SQL Analysis services are using the 
> Desktop
> Engine.
>
> What is the best way to move to the standard edition? I also need to 
> update
> the ODBC Driver to make it point to the Standard Edition. (How?)
>
> "Andrew J. Kelly" wrote:
>
>> It sounds like you have a DB that was created with MSDE or possably the 
>> SBS
>> edition of SQL Server.  What does @@VERSION show?
>>
>>
>> -- 
>> Andrew J. Kelly  SQL MVP
>>
>>
>> "Kam" <Kam@discussions.microsoft.com> wrote in message
>> news:44915EA7-BB76-4764-B013-F8CBCB128D35@microsoft.com...
>> > Andrew,
>> > If possible, can you explain to me why I experience an error when I
>> > manually
>> > increase the file size.
>> >
>> > under Database properties->Data Files,
>> > Change the space allocated from 2012 to 5000.
>> > Then an error come up "Error 1827: CREATE/ALTER DATABASE failed because
>> > the
>> > resulting cumulative database size would exceed your licensed limit of
>> > 2048
>> > MB per database"
>> >
>> > the version that I installed is SQL Developer Edition 2000, on W2K.
>> > with mutiple server instant, with analysis services running.
>> >
>> >
>> >
>> > "Andrew J. Kelly" wrote:
>> >
>> >> The developer edition does not have any restrictions like that as far 
>> >> as
>> >> I
>> >> know.  It is essentially the same as the Enterprise Edition.  It 
>> >> sounds
>> >> like
>> >> you have MSDE or the DeskTop Edition installed.  To upgrade to Std
>> >> Edition
>> >> you can not avoid rerunning setup for SQL Server to get to Std 
>> >> edition.
>> >> The
>> >> process is not bad though and this should guide you through it:
>> >>
>> >> http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q325023
>> >>
>> >>
>> >>  But the I would ensure you have good backups of all your user and 
>> >> system
>> >> db's before attempting anything.  These may help:
>> >>
>> >> 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://support.microsoft.com/?id=221465             Using WITH MOVE in 
>> >> a
>> >> Restore
>> >> 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://www.support.microsoft.com/?id=240872    How to Resolve 
>> >> Permission
>> >> Issues When a Database Is Moved Between SQL Servers
>> >> http://www.sqlservercentral.com/scripts/scriptdetails.asp?scriptid=599
>> >> Restoring a .mdf
>> >> http://www.support.microsoft.com/?id=307775    Disaster Recovery 
>> >> Articles
>> >> for SQL Server
>> >>
>> >>
>> >>
>> >> -- 
>> >> Andrew J. Kelly  SQL MVP
>> >>
>> >>
>> >> "Kam" <Kam@discussions.microsoft.com> wrote in message
>> >> news:9EA92B28-59BB-4B68-8502-F80288B8F143@microsoft.com...
>> >> >I am reaching the db limit in Developer Edition 2000.
>> >> > So I would like to convert it to SQL Standard Edition 2000 with no
>> >> > change
>> >> > of
>> >> > my existing setting. I don't want to re-install and I want to keep 
>> >> > the
>> >> > server
>> >> > name, DTS, Analysis services, and mulitple instant of SQL server.
>> >> >
>> >> > Is there any way to overcome the DB limit in Developer Edition 2000 
>> >> > or
>> >> > change it to Standard Edition without uninstall the Developer 
>> >> > edition,
>> >> > then
>> >> > install the standard edition?
>> >>
>> >>
>> >>
>>
>>
>> 


Relevant Pages

  • Re: SharePoint Services 3.0 unable to display content
    ... looking at the database table information, ... Microsoft Windows SharePoint Services 2.0 ... Can we asume you mean SQL Server 2005? ... The upgrade identified that there was a previous ...
    (microsoft.public.sharepoint.windowsservices)
  • Re: High availability
    ... Thanks Geoff and Andrew for the good info, I guess my best bet is to scale up ... setting up sql server failover clustering, replication, High availability, ... Senior Database Administrator ...
    (microsoft.public.sqlserver.clustering)
  • Re: Upgrade from MSDE to SQL
    ... Hard to say whether the database is of any use to you now you are partway ... upgrade just in case. ... But FIRST I would in any case see if adding SQL Server ...
    (microsoft.public.sharepoint.windowsservices)
  • Re: Cannot view DB properties
    ... # Ran the setup and upgraded the existing SQL Server 8.00.818 to SQL Server ... owner was NULL after the UPgraded finished successfully. ... The proposed new database owner is already a user or aliased in the ... Sorry, I don't understand, what do you mean by "In-Place Upgrade"? ...
    (microsoft.public.sqlserver.security)
  • Re: Upgrade 2000 to 2005
    ... That way, if there is a failure in the upgrade process, you at ... Senior Database Administrator ... Real-world stuff I run across with SQL Server: ... side and move the databases but the hardware just aint there. ...
    (microsoft.public.sqlserver.clustering)