Re: Replace MSDE with SQL2000

From: Tibor Karaszi (tibor_please.no.email_karaszi_at_hotmail.nomail.com)
Date: 03/21/04


Date: Sun, 21 Mar 2004 10:28:52 +0100

ysh,

> We have since then installed SQL2000 and are accessing our DBs serviced by
> this server.

Above implies that you have both the MSDE that came with BE installed as
well as the SQL Server that came with SBS. Correct? I.e., you have two SQL
Server instances. One is possibly a default instance (you can have max one
default instance) and the other would then have to be a named instance. Or
both could be named instances.

However, you list only the version information for one instance in your
post, the MSDE instance.

The first thing to do is to determine how many instances you have installed.

Note that service pack installs are different between MSDE and the regular
SQL Server, as they use different setup engines.

Also, you cannot "change" and MSDE to become a regular SQL Server. You have
to install a regular SQL Server and then move your database or something to
that effect. Below are some references on how to move databases and
installations:

Moving SQL Server Databases
http://www.support.microsoft.com/?id=224071

Moving Databases between Servers
http://www.support.microsoft.com/?id=314546

Using WITH MOVE in a Restore to a New Location with Detach/Attach
http://support.microsoft.com/?id=221465

How To Transfer Logins and Passwords Between SQL Servers
http://www.support.microsoft.com/?id=246133

Mapping Logins & SIDs after a Restore
http://www.support.microsoft.com/?id=298897

Utility to map users to the correct login
http://www.dbmaint.com/SyncSqlLogins.asp

How to Resolve Permission Issues When a Database Is Moved Between SQL
Servers
http://www.support.microsoft.com/?id=240872

User Logon and/or Permission Errors After Restoring Dump
http://www.support.microsoft.com/?id=168001

Disaster Recovery Articles for SQL Server
http://www.support.microsoft.com/?id=307775

-- 
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"ysh" <ysh-nospam-@9online.fr> wrote in message
news:c3jdpg$a5k$2@apollon.grec.isp.9tel.net...
> HI,
>
> We are running SBS2000. On this same server box we have also installed
> Veritas BackupExec 9.0
>
> Unfortunately the installation path we adopted meant that BackupExec was
> installed before we installed the SQL2000 component included with SBS.
>
> We have since then installed SQL2000 and are accessing our DBs serviced by
> this server.
>
> Recently we attempted to do two things : apply sp3 to SQL2K, and update
> BackupExec to version 9.1.
> We were unsuccessful in both cases.
>
> Apparently we are running version MSDE :
>
>     Microsoft SQL Server  2000 - 8.00.760 (Intel X86)
>     Dec 17 2002 14:22:05
>
>     Copyright (c) 1988-2003 Microsoft Corporation  Desktop Engine on
Windows
> NT
>     5.0 (Build 2195: Service Pack 4)
>
> Is this a sort of SQL run-time ? Which was probably installed by
BackupExec.
>
> How can we tell W2K that it is harbouring a full fledged SQL2000 server
and
> not an MSDE one ?
> (registry tweak ?)
>
> Thanks in advance
>
> YSH
>
>


Relevant Pages

  • RE: How to configure WSS to use SQL server instead of MSDE
    ... This is why, in this post, I wanted to focus on only WSS features. ... Apparently WSS DOES NOT SUPPORT SQL Server since it has no tool (that we ... >>MSDE databases for its configuration and content ...
    (microsoft.public.sharepoint.windowsservices)
  • Cannot insert explicit value for identity...
    ... I am developing an integration process between two databases. ... The main database is the SQL Server, the MSDE will contain a really ...
    (comp.databases.ms-sqlserver)
  • Re: Newbie Questions
    ... I have noticed that some of the documentation talkes about SQL Server ... > MSDE is the old database engine there is now as well SQL server Express, ... > hard to find (mostly everything is done with scripting ASP style). ... How do I use the MSDE functionality in relation to databases? ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Change default to named instance??
    ... Take a backup of all databases ... Stop SQL Server and copy the MDF and LDF to a safe place ... Un Install the MSDE ... > conflicts with other app's msdes, I now want to use a named instance. ...
    (microsoft.public.sqlserver.msde)
  • Re: Relocate MSDE 2000 database?
    ... Most of the 2000 versions of SQL Server and thus MSDE have been pulled. ... It can be purchased for about $40 and can manage any version of SQL Server. ... It will be increasingly expensive to support no-supported databases as time goes on. ... post -- these databases are installed and deployed by 3rd party apps ...
    (microsoft.public.sqlserver.msde)