MSDE 2ksp3a TO SQL Server 2000, why is upgrade option disabled?

Hi,
I have latest version of MSDE on my win xp machine, I had installed a named version msde using the microsoft bootstrapper along with my application. During installation I had specified the datadir to be something like c:\program files\MyApp\Data
So far so good.
Now I am trying to install SQL Server 2000 dev edition on my computer and was hoping to upgrade this named instance of MSDE, but the upgrade option is disabled. All I can click on is "Create a new instance of SQL Server, or install Client Tools" and "Adv
anced options". Why is that. What am I missing. I read many times that upgrading named instance shouldn't be a problem.
I have to figure this out so that in future my client's can upgrade our MSDE named instance to SQL Server named instance if they need to..
Thanks
dev
correction, I had installed msde using the latest sql2ksp3 exe from microsoft.
thanks
dev
|||You can't upgrade MSDE to Developer Edition, you can only upgrade to SQL
Server 2000 Enterprise Edition or SQL Server 2000 Standard Edition.
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"dev" <anonymous@.discussions.microsoft.com> wrote in message
news:F366A797-A10F-4EAE-8AD7-1BC89ED470C4@.microsoft.com...
> Hi,
> I have latest version of MSDE on my win xp machine, I had installed a
named version msde using the microsoft bootstrapper along with my
application. During installation I had specified the datadir to be
something like c:\program files\MyApp\Data
> So far so good.
> Now I am trying to install SQL Server 2000 dev edition on my computer and
was hoping to upgrade this named instance of MSDE, but the upgrade option is
disabled. All I can click on is "Create a new instance of SQL Server, or
install Client Tools" and "Advanced options". Why is that. What am I
missing. I read many times that upgrading named instance shouldn't be a
problem.
> I have to figure this out so that in future my client's can upgrade our
MSDE named instance to SQL Server named instance if they need to..
> Thanks
> dev
>
|||Jasper thanks for the reply. Where can I find the document which states MSDE can be upgraded to which versions.
Does that mean that my client will have to invest in a server (NT 4.0 Server OR NT 4.0 Enterprise Server OR Windows 2000 server OR Windows 2000 Advanced Server..) if they wish to upgrade from MSDE to SQL Server...
thanks
dev
|||got it, thanks
http://support.microsoft.com/default...b;en-us;823462
|||They'll need a server operating system e.g. Windows 2000 Server or Windows
2003 Standard to install SQL2000 Standard
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"dev" <anonymous@.discussions.microsoft.com> wrote in message
news:3F461785-F5A1-491F-9A4E-8ED5462409AE@.microsoft.com...
> Jasper thanks for the reply. Where can I find the document which states
MSDE can be upgraded to which versions.
> Does that mean that my client will have to invest in a server (NT 4.0
Server OR NT 4.0 Enterprise Server OR Windows 2000 server OR Windows 2000
Advanced Server..) if they wish to upgrade from MSDE to SQL Server...
> thanks
> dev

MSDE 2ksp3a TO SQL Server 2000, why is upgrade option disabled?

Hi
I have latest version of MSDE on my win xp machine, I had installed a named version msde using the microsoft bootstrapper along with my application. During installation I had specified the datadir to be something like c:\program files\MyApp\Dat
So far so good
Now I am trying to install SQL Server 2000 dev edition on my computer and was hoping to upgrade this named instance of MSDE, but the upgrade option is disabled. All I can click on is "Create a new instance of SQL Server, or install Client Tools" and "Advanced options". Why is that. What am I missing. I read many times that upgrading named instance shouldn't be a problem
I have to figure this out so that in future my client's can upgrade our MSDE named instance to SQL Server named instance if they need to.
Thank
deYou can't upgrade MSDE to Developer Edition, you can only upgrade to SQL
Server 2000 Enterprise Edition or SQL Server 2000 Standard Edition.
--
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"dev" <anonymous@.discussions.microsoft.com> wrote in message
news:F366A797-A10F-4EAE-8AD7-1BC89ED470C4@.microsoft.com...
> Hi,
> I have latest version of MSDE on my win xp machine, I had installed a
named version msde using the microsoft bootstrapper along with my
application. During installation I had specified the datadir to be
something like c:\program files\MyApp\Data
> So far so good.
> Now I am trying to install SQL Server 2000 dev edition on my computer and
was hoping to upgrade this named instance of MSDE, but the upgrade option is
disabled. All I can click on is "Create a new instance of SQL Server, or
install Client Tools" and "Advanced options". Why is that. What am I
missing. I read many times that upgrading named instance shouldn't be a
problem.
> I have to figure this out so that in future my client's can upgrade our
MSDE named instance to SQL Server named instance if they need to..
> Thanks
> dev
>|||Jasper thanks for the reply. Where can I find the document which states MSDE can be upgraded to which versions.
Does that mean that my client will have to invest in a server (NT 4.0 Server OR NT 4.0 Enterprise Server OR Windows 2000 server OR Windows 2000 Advanced Server..) if they wish to upgrade from MSDE to SQL Server...
thank
dev|||got it, thanks
http://support.microsoft.com/default.aspx?scid=kb;en-us;823462|||They'll need a server operating system e.g. Windows 2000 Server or Windows
2003 Standard to install SQL2000 Standard
--
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"dev" <anonymous@.discussions.microsoft.com> wrote in message
news:3F461785-F5A1-491F-9A4E-8ED5462409AE@.microsoft.com...
> Jasper thanks for the reply. Where can I find the document which states
MSDE can be upgraded to which versions.
> Does that mean that my client will have to invest in a server (NT 4.0
Server OR NT 4.0 Enterprise Server OR Windows 2000 server OR Windows 2000
Advanced Server..) if they wish to upgrade from MSDE to SQL Server...
> thanks
> dev

msde 2000 verify instance

I'm trying to write logic that verifies whether or not a named instance
already exists on a PC using C#. Is there a way to do this?
hi,
"liz23" <liz23@.discussions.microsoft.com> ha scritto nel messaggio
news:5C36ED99-6FC3-4D66-9775-0E6958DEE554@.microsoft.com...
> I'm trying to write logic that verifies whether or not a named instance
> already exists on a PC using C#. Is there a way to do this?
you can try several methods... you can (locally) query the windows registry
for the
HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\
InstalledInstances
which return a list of all locally installed instances, where "MSSQLSERVER"
is the default instance...
you can query the SQLDMO.Application .ListAvailableSQLServers method to
return all available instance of the lan or SQLDMO.SQLServer2
..ListInstalledInstances("ServerName") for all available instaces on the
specified server...
by the way, .ListAvailableServer uses ODBC function SQLBrowseConnect()
provided by ODBC libraries installed by Mdac;
this is a mechanism working in broadcast calls, which result never are
conclusive and consistent, becouse results are influenced of various
servers's answer states, answer time, etc.
Until Mdac 2.5, SQLBrowseConnect function works based on a NetBIOS
broadcast, on which SQL Servers respond (Default protocol for SQL Server
7.0), while in SQL Server 2000 the rules changed, because the default client
protocol changed to TCP/IP and now a UDP broadcast is used, beside a NetBIOS
broadcast, listening on port 1434:
which is using a UDP broadcast on port 1434, if instance do not listen or
not respond on time they will not be part of the enumeration.
Some basic rules for 7.0 are:
- SQL Servers have to be running on Windows NT or Windows 2000 and have to
listen on Named Pipes, that is why in 7.0 Windows 9x SQL Servers will never
show up, because they do not listen on Named Pipes.
- The SQL Server has to be running in order to respond on the broadcast.
There is a gray window of 15 minutes after shutdown, where a browse master
in the domain may respond on the broadcast and answer.
- If you have routers in your network, that do not pass on NetBIOS
broadcasts, this might limit your scope of the broadcast.
- Only servers within the same NT domain (or trust) will get enumerated.
In SQL Server 2000 using MDAC 2.6 this changes a little, because now the
default protocol has been changed to be TCP/IP sockets and instead of a
NetBIOS broadcast, they use a TCP UDP to detect the servers. The same logic
still applies roughly.
- SQL Server that are running
- SQL Server that listening on TCP/IP
- Running on Windows NT or Windows 2000 or Windows 9x
- If you use routers and these are configured not to pass UDP broadcasts,
only machines within the same subnet show up.
Upgrading to Service Pack 2 of SQL Server 2000 is required in order to have
..ListAvailableServer method to work properly, becouse precding release of
Sql-DMO Components of Sql Server 2000 present a bug in this area.
The Service Pack 3a introduced some new amenity in order to prevent MSDE
2000 to be hit by Internet worms like Slammer and Saphire virus and to
increase security, so that Microsoft decided to default for disabling
SuperSockets Network Protocols on new MSDE 2000 installation.
Instances of SQL Server 2000 SP3a or MSDE 2000 SP3a will stop listening on
UDP port 1434 when they are configured to not listen on any network
protocols. This will stop enlisting these servers.
other way to locate end enum SQL Server on the lan are available at
http://www.sqldev.net/misc/EnumSQLSvr.htm
http://www.sqldev.net/misc/ListSQLSvr.htm
http://www.sqldev.net/misc/OleDbEnum.htm
or try connecting to a specified instance name via Ado.Net, if you geuss a
defined instance is available... but keep the connection time-out very low
=;-D
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

MSDE 2000 named instance with my application

I am writing an application and wish to distribute MSDE with it.
I was considering using a batch file to do the install using the line
setup INSTANCENAME="InstanceName" SAPWD="AStrongSAPwd"
However, the next step would be to call osql to either script the schema or
sp_attach_db the database. Well this raises the issue of once installed
with a named instance how do I do osql -E -S MACHINENAME\InstanceName
without knowing it ahead of time? Is there perhaps 1. an easier way or 2. a
different syntax to achieving it? I am pretty sure I will run into more
grief when attempting to set up the ODBC connections also.
Maybe I'd just be better off rewriting this to use an Access database
instead
hi Bradley,
"Bradley M. Small" <BSmall@.XNOSPAMXmjsi.com> ha scritto nel messaggio
news:ejW7scifEHA.1424@.tk2msftngp13.phx.gbl...
> I am writing an application and wish to distribute MSDE with it.
> I was considering using a batch file to do the install using the line
> setup INSTANCENAME="InstanceName" SAPWD="AStrongSAPwd"
> However, the next step would be to call osql to either script the schema
or
> sp_attach_db the database. Well this raises the issue of once installed
> with a named instance how do I do osql -E -S MACHINENAME\InstanceName
> without knowing it ahead of time? Is there perhaps 1. an easier way or 2.
a
> different syntax to achieving it? I am pretty sure I will run into more
> grief when attempting to set up the ODBC connections also.
> Maybe I'd just be better off rewriting this to use an Access database
> instead
you don't actually need to reference the Machine name... just refer to it as
"(local)" or "."
so, the full instance name will be
(local)\InstanceName
stay this MSDE... you'll love it =;-D
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:2npor3F3baroU1@.uni-berlin.de...
> hi Bradley,
> "Bradley M. Small" <BSmall@.XNOSPAMXmjsi.com> ha scritto nel messaggio
> news:ejW7scifEHA.1424@.tk2msftngp13.phx.gbl...
> you don't actually need to reference the Machine name... just refer to it
as
> "(local)" or "."
> so, the full instance name will be
> (local)\InstanceName
> stay this MSDE... you'll love it =;-D
> --
Great!!! Seemed like there had to be a better syntax
Now, all I need to figure out is how to add the odbc connection from a batch
file. Is that even possible?

MSDE 2000 Named instance in conjunction with SQL server 7

I have SQL server 7 running as a default instance and I'm trying to install
MSDE 2000. I was able to install it as a named instance by running the
following:
setup.exe SAPWD="password" INSTANCENAME="named_instance"
Now I can not connect to the named instance with OSQL. What do I need to do
to connect properly?
Hi,
Try to connect to the instance as servername\named_instance
Example: If your machine name is MyServer1 and your named instance is
Cyclops then you would refer to the server as MyServer1\Cyclops. If this
will not work for you in the long run, you can always set up an alias on
your client through the Client Network Utility to refer to it in a more
conventional manner.
-Jose Molina
"iranpessar@.hotmail.com" <iranpessarhotmailcom@.discussions.microsoft.com>
wrote in message news:1FB9C0FC-639B-4B6E-A4EC-6623B70F3F78@.microsoft.com...
>I have SQL server 7 running as a default instance and I'm trying to install
> MSDE 2000. I was able to install it as a named instance by running the
> following:
> setup.exe SAPWD="password" INSTANCENAME="named_instance"
> Now I can not connect to the named instance with OSQL. What do I need to
> do
> to connect properly?

MSDE 2000 Named instance in conjunction with SQL server 7

I have SQL server 7 running as a default instance and I'm trying to install
MSDE 2000. I was able to install it as a named instance by running the
following:
setup.exe SAPWD="password" INSTANCENAME="named_instance"
Now I can not connect to the named instance with OSQL. What do I need to do
to connect properly?Hi,
Try to connect to the instance as servername\named_instance
Example: If your machine name is MyServer1 and your named instance is
Cyclops then you would refer to the server as MyServer1\Cyclops. If this
will not work for you in the long run, you can always set up an alias on
your client through the Client Network Utility to refer to it in a more
conventional manner.
-Jose Molina
"iranpessar@.hotmail.com" <iranpessarhotmailcom@.discussions.microsoft.com>
wrote in message news:1FB9C0FC-639B-4B6E-A4EC-6623B70F3F78@.microsoft.com...
>I have SQL server 7 running as a default instance and I'm trying to install
> MSDE 2000. I was able to install it as a named instance by running the
> following:
> setup.exe SAPWD="password" INSTANCENAME="named_instance"
> Now I can not connect to the named instance with OSQL. What do I need to
> do
> to connect properly?sql

MSDE 2000 install on SQL 2000

Hello,
I have installed MSDE 2000 on Win Server 2003 with instance name brprof,
there SQL Server 2000 already installed as a local instance named SBGBHO.
Now, I registered my new MSDE 2000 on enterprise manager, registration done
successfully, but it display following error
LOGIN FAILED FOR USER SA : REASON NOT ASSOCIATED WITH TRUSTED SQL SERVER
CONNECTION
HARSHA.
hi Harsha,
Harsha Shah wrote:
> Hello,
> I have installed MSDE 2000 on Win Server 2003 with instance name
> brprof, there SQL Server 2000 already installed as a local instance
> named SBGBHO. Now, I registered my new MSDE 2000 on enterprise
> manager, registration done successfully, but it display following
> error
> LOGIN FAILED FOR USER SA : REASON NOT ASSOCIATED WITH TRUSTED SQL
> SERVER CONNECTION
MSDE installs by default only allowing trusted WinNT connections... you can
change this behavior, allowing standard SQL Server connection at install
time providing the
SECURITYMODE=SQL
parameter to the setup.exe boostrap installer, or later accessing the
windows registry, as described in
http://support.microsoft.com/default...b;en-us;285097
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

MSDE

Not able to connect to named instance of MSDE
C:\>osql -E -S NT14954\MSSQL$MYMSDE1
[DBMSLPCN]SQL Server does not exist or access denied.
[DBMSLPCN]ConnectionOpen (Connect()).
HelpHi,
See if the SQL Server service is running. If running then open the SQL
Server error log and see the name of the SQL server.
After that use the same name to connect.
Thanks
Hari
SQL Server MVP
"docsql" <docsql@.noemail.nospam> wrote in message
news:%23YPOANkuFHA.128@.TK2MSFTNGP09.phx.gbl...
> Not able to connect to named instance of MSDE
> C:\>osql -E -S NT14954\MSSQL$MYMSDE1
> [DBMSLPCN]SQL Server does not exist or access denied.
> [DBMSLPCN]ConnectionOpen (Connect()).
>
> Help
>|||The name of your MSDE instance is NT14954\MYMSDE1 so to connect use
osql -E -S NT14954\MYMSDE1
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
"docsql" <docsql@.noemail.nospam> wrote in message
news:%23YPOANkuFHA.128@.TK2MSFTNGP09.phx.gbl...
> Not able to connect to named instance of MSDE
> C:\>osql -E -S NT14954\MSSQL$MYMSDE1
> [DBMSLPCN]SQL Server does not exist or access denied.
> [DBMSLPCN]ConnectionOpen (Connect()).
>
> Help
>

MSDE

Not able to connect to named instance of MSDE
C:\>osql -E -S NT14954\MSSQL$MYMSDE1
[DBMSLPCN]SQL Server does not exist or access denied.
[DBMSLPCN]ConnectionOpen (Connect()).
Help
Hi,
See if the SQL Server service is running. If running then open the SQL
Server error log and see the name of the SQL server.
After that use the same name to connect.
Thanks
Hari
SQL Server MVP
"docsql" <docsql@.noemail.nospam> wrote in message
news:%23YPOANkuFHA.128@.TK2MSFTNGP09.phx.gbl...
> Not able to connect to named instance of MSDE
> C:\>osql -E -S NT14954\MSSQL$MYMSDE1
> [DBMSLPCN]SQL Server does not exist or access denied.
> [DBMSLPCN]ConnectionOpen (Connect()).
>
> Help
>
|||The name of your MSDE instance is NT14954\MYMSDE1 so to connect use
osql -E -S NT14954\MYMSDE1
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
"docsql" <docsql@.noemail.nospam> wrote in message
news:%23YPOANkuFHA.128@.TK2MSFTNGP09.phx.gbl...
> Not able to connect to named instance of MSDE
> C:\>osql -E -S NT14954\MSSQL$MYMSDE1
> [DBMSLPCN]SQL Server does not exist or access denied.
> [DBMSLPCN]ConnectionOpen (Connect()).
>
> Help
>

MSDE

Not able to connect to named instance of MSDE
C:\>osql -E -S NT14954\MSSQL$MYMSDE1
[DBMSLPCN]SQL Server does not exist or access denied.
[DBMSLPCN]ConnectionOpen (Connect()).
HelpHi,
See if the SQL Server service is running. If running then open the SQL
Server error log and see the name of the SQL server.
After that use the same name to connect.
Thanks
Hari
SQL Server MVP
"docsql" <docsql@.noemail.nospam> wrote in message
news:%23YPOANkuFHA.128@.TK2MSFTNGP09.phx.gbl...
> Not able to connect to named instance of MSDE
> C:\>osql -E -S NT14954\MSSQL$MYMSDE1
> [DBMSLPCN]SQL Server does not exist or access denied.
> [DBMSLPCN]ConnectionOpen (Connect()).
>
> Help
>|||The name of your MSDE instance is NT14954\MYMSDE1 so to connect use
osql -E -S NT14954\MYMSDE1
--
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
"docsql" <docsql@.noemail.nospam> wrote in message
news:%23YPOANkuFHA.128@.TK2MSFTNGP09.phx.gbl...
> Not able to connect to named instance of MSDE
> C:\>osql -E -S NT14954\MSSQL$MYMSDE1
> [DBMSLPCN]SQL Server does not exist or access denied.
> [DBMSLPCN]ConnectionOpen (Connect()).
>
> Help
>