Basic "getting started" Info on MSDE 2000?

Hello,

I am looking for basic info on installing and using MSDE.

I am trying to install and play with MSDE on my PC (Win2000). I
finally managed to work my way through installation, and named
instances but I am finding no information on how to simply START the
database engine and get to a sql prompt! I have manually started the
MSSQL and SQLAGENT services, and tried running sqlservr.exe and
osql.exe (just guessing) without success. Can anyone refer me to a
document that gives this BASIC information!?(bidalah@.yahoo.com) writes:
> I am looking for basic info on installing and using MSDE.
> I am trying to install and play with MSDE on my PC (Win2000). I
> finally managed to work my way through installation, and named
> instances but I am finding no information on how to simply START the
> database engine and get to a sql prompt! I have manually started the
> MSSQL and SQLAGENT services, and tried running sqlservr.exe and
> osql.exe (just guessing) without success. Can anyone refer me to a
> document that gives this BASIC information!?

SQL Server runs as a service, and you should start it from the
Services Applet in the Control Panel (under Administrative tools). I
don't if you get SQL Server Manager with MSDE; if you do, you can use
this tool a well. The same applies to SQL Server Agent.

You can start sqlservr.exe from the command line, but this is advanced
usage.

OSQL is a client, and this you run from the command line. To connect
with integrated security say:

osql -E -S .\INSTANCENAME

replace INSTANCENAME with the actual name of your instance.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp

Backward Compatibility Upgrade failed on Service Pack 1 for SQL Server 2005

Not sure if this gets fixed on a restart, but the Backward Compatibility upgrade/piece failed on service pack 1 install for SQL Server 2005. Here is the log output. Anyone experience this?

05/19/2006 08:58:27.648 ================================================================================
05/19/2006 08:58:27.648 Hotfix package launched
05/19/2006 09:00:04.368 Attempting to install instance: SQL Server Native Client
05/19/2006 09:00:04.383 Attempting to install target: CLARITY
05/19/2006 09:00:04.383 Attempting to install file: sqlncli.msi
05/19/2006 09:00:04.399 Attempting to install file: \\<server>\s$\917f50731dade382ab1b\HotFixSqlncli\Files\sqlncli.msi
05/19/2006 09:00:04.399 Creating MSI install log file at: C:\WINDOWS\Hotfix\Redist9\Logs\Redist9_Hotfix_KB913090_sqlncli.msi.log
05/19/2006 09:00:04.415 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
05/19/2006 09:00:04.415 Failed to read registry key: Debug
05/19/2006 09:00:51.040 MSP returned 3010: A restart is required to complete the install. This message is indicative of a success. This does not include installs where the ForceReboot action is run. This error code is not available on Windows Installer version 1.0.
05/19/2006 09:00:51.118 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
05/19/2006 09:00:51.118 Failed to read registry key: Debug
05/19/2006 09:00:51.118 Pending reboot, successfully installed file: \\<server>\s$\917f50731dade382ab1b\HotFixSqlncli\Files\sqlncli.msi
05/19/2006 09:00:51.134 Successfully installed target: <SERVER>
05/19/2006 09:00:51.134 Successfully installed instance: SQL Server Native Client
05/19/2006 09:00:51.134
05/19/2006 09:00:51.134 Product Status Summary:
05/19/2006 09:00:51.134 Product: SQL Server Native Client
05/19/2006 09:00:51.134 SQL Server Native Client (RTM ) - Reboot Required
05/19/2006 09:00:51.134
05/19/2006 09:00:51.134 Product: Setup Support Files
05/19/2006 09:00:51.134 Setup Support Files (RTM ) - Not Applied
05/19/2006 09:00:51.150
05/19/2006 09:00:51.150 Product: Database Services
05/19/2006 09:00:51.150 Database Services (RTM 1399 ENU) - Not Applied
05/19/2006 09:00:51.150 Reporting Services (RTM 1399 ENU) - Not Applied
05/19/2006 09:00:51.150
05/19/2006 09:00:51.150 Product: Notification Services
05/19/2006 09:00:51.150 Notification Services (RTM 1399 ENU) - Not Applied
05/19/2006 09:00:51.150
05/19/2006 09:00:51.150 Product: Integration Services
05/19/2006 09:00:51.150 Integration Services (RTM 1399 ENU) - Not Applied
05/19/2006 09:00:51.150
05/19/2006 09:00:51.150 Product: Client Components
05/19/2006 09:00:51.165 Client Components (RTM 1399 ENU) - Not Applied
05/19/2006 09:00:51.165
05/19/2006 09:00:51.165 Product: MSXML 6.0 Parser
05/19/2006 09:00:51.165 MSXML 6.0 Parser (RTM ) - Not Applied
05/19/2006 09:00:51.165
05/19/2006 09:00:51.165 Product: SQLXML4
05/19/2006 09:00:51.165 SQLXML4 (RTM ) - Not Applied
05/19/2006 09:00:51.165
05/19/2006 09:00:51.165 Product: Backward Compatibility
05/19/2006 09:00:51.165 Backward Compatibility (RTM ) - Not Applied
05/19/2006 09:00:51.181
05/19/2006 09:00:51.181 Product: Microsoft SQL Server VSS Writer
05/19/2006 09:00:51.181 Microsoft SQL Server VSS Writer (RTM ) - Not Applied
05/19/2006 09:00:51.181

Are there any other logs created other than this one? If so, can you search for the "return value 3" in them and send the +/- 10 lines on each side of that error for us to debug?

Thanks,
Samuel Lester (MSFT)

|||

From your log info, it does not look like Hotfix even attempted to install on Backward Compatibility redist.

05/19/2006 09:00:51.165 Product: Backward Compatibility
05/19/2006 09:00:51.165 Backward Compatibility (RTM ) - Not Applied

Please reboot and try again. May be SNAC reboot has halted the installation until reboot.

|||

did you find a solution for this? I have the same problem. I am running a named instance of sql server 2005 standard edition and a default instance of sql server 2000 enterprise. I removed the default instance to install a new version of sql server 2005 as default, but I am unable to install it because of the backward compatability. I have managed to put 2000 back on as the default instance. Now i cannot apply service pack 1 to my named instance and i cannot install analysis server. I have tried to run sqlserver2005_bc.msi but get the error

'failed because a higher version already exists on the machine'

Is it safe to uninstall backward compatability and reinstall it?

Thanks,

Kerry

|||This has been so long ago, I don't remember what came out of this. Sorry for not catching your response sooner.

Backward Compatibility Upgrade failed on Service Pack 1 for SQL Server 2005

Not sure if this gets fixed on a restart, but the Backward Compatibility upgrade/piece failed on service pack 1 install for SQL Server 2005. Here is the log output. Anyone experience this?

05/19/2006 08:58:27.648 ================================================================================
05/19/2006 08:58:27.648 Hotfix package launched
05/19/2006 09:00:04.368 Attempting to install instance: SQL Server Native Client
05/19/2006 09:00:04.383 Attempting to install target: CLARITY
05/19/2006 09:00:04.383 Attempting to install file: sqlncli.msi
05/19/2006 09:00:04.399 Attempting to install file: \\<server>\s$\917f50731dade382ab1b\HotFixSqlncli\Files\sqlncli.msi
05/19/2006 09:00:04.399 Creating MSI install log file at: C:\WINDOWS\Hotfix\Redist9\Logs\Redist9_Hotfix_KB913090_sqlncli.msi.log
05/19/2006 09:00:04.415 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
05/19/2006 09:00:04.415 Failed to read registry key: Debug
05/19/2006 09:00:51.040 MSP returned 3010: A restart is required to complete the install. This message is indicative of a success. This does not include installs where the ForceReboot action is run. This error code is not available on Windows Installer version 1.0.
05/19/2006 09:00:51.118 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
05/19/2006 09:00:51.118 Failed to read registry key: Debug
05/19/2006 09:00:51.118 Pending reboot, successfully installed file: \\<server>\s$\917f50731dade382ab1b\HotFixSqlncli\Files\sqlncli.msi
05/19/2006 09:00:51.134 Successfully installed target: <SERVER>
05/19/2006 09:00:51.134 Successfully installed instance: SQL Server Native Client
05/19/2006 09:00:51.134
05/19/2006 09:00:51.134 Product Status Summary:
05/19/2006 09:00:51.134 Product: SQL Server Native Client
05/19/2006 09:00:51.134 SQL Server Native Client (RTM ) - Reboot Required
05/19/2006 09:00:51.134
05/19/2006 09:00:51.134 Product: Setup Support Files
05/19/2006 09:00:51.134 Setup Support Files (RTM ) - Not Applied
05/19/2006 09:00:51.150
05/19/2006 09:00:51.150 Product: Database Services
05/19/2006 09:00:51.150 Database Services (RTM 1399 ENU) - Not Applied
05/19/2006 09:00:51.150 Reporting Services (RTM 1399 ENU) - Not Applied
05/19/2006 09:00:51.150
05/19/2006 09:00:51.150 Product: Notification Services
05/19/2006 09:00:51.150 Notification Services (RTM 1399 ENU) - Not Applied
05/19/2006 09:00:51.150
05/19/2006 09:00:51.150 Product: Integration Services
05/19/2006 09:00:51.150 Integration Services (RTM 1399 ENU) - Not Applied
05/19/2006 09:00:51.150
05/19/2006 09:00:51.150 Product: Client Components
05/19/2006 09:00:51.165 Client Components (RTM 1399 ENU) - Not Applied
05/19/2006 09:00:51.165
05/19/2006 09:00:51.165 Product: MSXML 6.0 Parser
05/19/2006 09:00:51.165 MSXML 6.0 Parser (RTM ) - Not Applied
05/19/2006 09:00:51.165
05/19/2006 09:00:51.165 Product: SQLXML4
05/19/2006 09:00:51.165 SQLXML4 (RTM ) - Not Applied
05/19/2006 09:00:51.165
05/19/2006 09:00:51.165 Product: Backward Compatibility
05/19/2006 09:00:51.165 Backward Compatibility (RTM ) - Not Applied
05/19/2006 09:00:51.181
05/19/2006 09:00:51.181 Product: Microsoft SQL Server VSS Writer
05/19/2006 09:00:51.181 Microsoft SQL Server VSS Writer (RTM ) - Not Applied
05/19/2006 09:00:51.181

Are there any other logs created other than this one? If so, can you search for the "return value 3" in them and send the +/- 10 lines on each side of that error for us to debug?

Thanks,
Samuel Lester (MSFT)

|||

From your log info, it does not look like Hotfix even attempted to install on Backward Compatibility redist.

05/19/2006 09:00:51.165 Product: Backward Compatibility
05/19/2006 09:00:51.165 Backward Compatibility (RTM ) - Not Applied

Please reboot and try again. May be SNAC reboot has halted the installation until reboot.

|||

did you find a solution for this? I have the same problem. I am running a named instance of sql server 2005 standard edition and a default instance of sql server 2000 enterprise. I removed the default instance to install a new version of sql server 2005 as default, but I am unable to install it because of the backward compatability. I have managed to put 2000 back on as the default instance. Now i cannot apply service pack 1 to my named instance and i cannot install analysis server. I have tried to run sqlserver2005_bc.msi but get the error

'failed because a higher version already exists on the machine'

Is it safe to uninstall backward compatability and reinstall it?

Thanks,

Kerry

|||This has been so long ago, I don't remember what came out of this. Sorry for not catching your response sooner.

Backward Compatibility Upgrade failed on Service Pack 1 for SQL Server 2005

Not sure if this gets fixed on a restart, but the Backward Compatibility upgrade/piece failed on service pack 1 install for SQL Server 2005. Here is the log output. Anyone experience this?

05/19/2006 08:58:27.648 ================================================================================
05/19/2006 08:58:27.648 Hotfix package launched
05/19/2006 09:00:04.368 Attempting to install instance: SQL Server Native Client
05/19/2006 09:00:04.383 Attempting to install target: CLARITY
05/19/2006 09:00:04.383 Attempting to install file: sqlncli.msi
05/19/2006 09:00:04.399 Attempting to install file: \\<server>\s$\917f50731dade382ab1b\HotFixSqlncli\Files\sqlncli.msi
05/19/2006 09:00:04.399 Creating MSI install log file at: C:\WINDOWS\Hotfix\Redist9\Logs\Redist9_Hotfix_KB913090_sqlncli.msi.log
05/19/2006 09:00:04.415 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
05/19/2006 09:00:04.415 Failed to read registry key: Debug
05/19/2006 09:00:51.040 MSP returned 3010: A restart is required to complete the install. This message is indicative of a success. This does not include installs where the ForceReboot action is run. This error code is not available on Windows Installer version 1.0.
05/19/2006 09:00:51.118 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
05/19/2006 09:00:51.118 Failed to read registry key: Debug
05/19/2006 09:00:51.118 Pending reboot, successfully installed file: \\<server>\s$\917f50731dade382ab1b\HotFixSqlncli\Files\sqlncli.msi
05/19/2006 09:00:51.134 Successfully installed target: <SERVER>
05/19/2006 09:00:51.134 Successfully installed instance: SQL Server Native Client
05/19/2006 09:00:51.134
05/19/2006 09:00:51.134 Product Status Summary:
05/19/2006 09:00:51.134 Product: SQL Server Native Client
05/19/2006 09:00:51.134 SQL Server Native Client (RTM ) - Reboot Required
05/19/2006 09:00:51.134
05/19/2006 09:00:51.134 Product: Setup Support Files
05/19/2006 09:00:51.134 Setup Support Files (RTM ) - Not Applied
05/19/2006 09:00:51.150
05/19/2006 09:00:51.150 Product: Database Services
05/19/2006 09:00:51.150 Database Services (RTM 1399 ENU) - Not Applied
05/19/2006 09:00:51.150 Reporting Services (RTM 1399 ENU) - Not Applied
05/19/2006 09:00:51.150
05/19/2006 09:00:51.150 Product: Notification Services
05/19/2006 09:00:51.150 Notification Services (RTM 1399 ENU) - Not Applied
05/19/2006 09:00:51.150
05/19/2006 09:00:51.150 Product: Integration Services
05/19/2006 09:00:51.150 Integration Services (RTM 1399 ENU) - Not Applied
05/19/2006 09:00:51.150
05/19/2006 09:00:51.150 Product: Client Components
05/19/2006 09:00:51.165 Client Components (RTM 1399 ENU) - Not Applied
05/19/2006 09:00:51.165
05/19/2006 09:00:51.165 Product: MSXML 6.0 Parser
05/19/2006 09:00:51.165 MSXML 6.0 Parser (RTM ) - Not Applied
05/19/2006 09:00:51.165
05/19/2006 09:00:51.165 Product: SQLXML4
05/19/2006 09:00:51.165 SQLXML4 (RTM ) - Not Applied
05/19/2006 09:00:51.165
05/19/2006 09:00:51.165 Product: Backward Compatibility
05/19/2006 09:00:51.165 Backward Compatibility (RTM ) - Not Applied
05/19/2006 09:00:51.181
05/19/2006 09:00:51.181 Product: Microsoft SQL Server VSS Writer
05/19/2006 09:00:51.181 Microsoft SQL Server VSS Writer (RTM ) - Not Applied
05/19/2006 09:00:51.181

Are there any other logs created other than this one? If so, can you search for the "return value 3" in them and send the +/- 10 lines on each side of that error for us to debug?

Thanks,
Samuel Lester (MSFT)

|||

From your log info, it does not look like Hotfix even attempted to install on Backward Compatibility redist.

05/19/2006 09:00:51.165 Product: Backward Compatibility
05/19/2006 09:00:51.165 Backward Compatibility (RTM ) - Not Applied

Please reboot and try again. May be SNAC reboot has halted the installation until reboot.

|||

did you find a solution for this? I have the same problem. I am running a named instance of sql server 2005 standard edition and a default instance of sql server 2000 enterprise. I removed the default instance to install a new version of sql server 2005 as default, but I am unable to install it because of the backward compatability. I have managed to put 2000 back on as the default instance. Now i cannot apply service pack 1 to my named instance and i cannot install analysis server. I have tried to run sqlserver2005_bc.msi but get the error

'failed because a higher version already exists on the machine'

Is it safe to uninstall backward compatability and reinstall it?

Thanks,

Kerry

|||This has been so long ago, I don't remember what came out of this. Sorry for not catching your response sooner.