Named subscription is greyed out

The system consists of one SQL 2000 Server (Distributor and Publisher) and
several subscribers running MSDE 2000 and Merge Replication. Every
Subscriber connects to the publisher using Pull Subscription, but the choice
of selecting "No, This is a named subscription" is grayed out when
establishing the subscription. I therefore have to pick Anonymous
subscription... Why?
You'll need to register the subscribers first.
With the MSDE subscriber connected to your publisher, in Enterprise Mgr:
right click Replication and select the Config. Publishers, Subscriber and
Distributors option. On the Subscribers tab, select the box next to the
Subscribers to register them. Enter the connecting account using the ...
button. Then re-create the pull subscription.
Had the same problem myself recently.
Steve Halfacre
Synapsis, UK
<hallvardsc@.hotmail.com> wrote in message
news:%23dPPwIeLEHA.340@.TK2MSFTNGP11.phx.gbl...
> The system consists of one SQL 2000 Server (Distributor and Publisher) and
> several subscribers running MSDE 2000 and Merge Replication. Every
> Subscriber connects to the publisher using Pull Subscription, but the
choice
> of selecting "No, This is a named subscription" is grayed out when
> establishing the subscription. I therefore have to pick Anonymous
> subscription... Why?
>
>
sql

Named Pipes Provider, error: 40 - Could not open a connection

Ok,
I've spent a bunch of hours trying to figure out how to connect to SQL
Server 2005. I have MSDE 2005, IIS 6.0 and ASP.NET configured on my laptop.
I can run ASP.net code with no problem. I can access SQL Server from the
command line using osql with no problem.
But trying to access sql server 2005 from asp.net yields the following
message:
System.Data.SqlClient.SqlException: An error has occurred while establishing
a connection to the server. When connecting to SQL Server 2005, this failure
may be caused by the fact that under the default settings SQL Server does not
allow remote connections. (provider: Named Pipes Provider, error: 40 - Could
not open a connection to SQL Server)
Can someone help me with this? I have both tcp/ip and named pipes enabled.
--
ThanksCan you post your connection string?
specifying
Network=DBMSSOCN
in your connection string will cause it to use tcp instead of named pipes,
which is less error prone.
See here for more details:
http://www.aspfaq.com/show.asp?id=2126
Also, check out the post regarding connections to sql express.
http://www.aspfaq.com/sql2005/show.asp?id=3
HTH
--
Ryan Powers
Clarity Consulting
http://www.claritycon.com
"Greg" wrote:
> Ok,
> I've spent a bunch of hours trying to figure out how to connect to SQL
> Server 2005. I have MSDE 2005, IIS 6.0 and ASP.NET configured on my laptop.
> I can run ASP.net code with no problem. I can access SQL Server from the
> command line using osql with no problem.
> But trying to access sql server 2005 from asp.net yields the following
> message:
> System.Data.SqlClient.SqlException: An error has occurred while establishing
> a connection to the server. When connecting to SQL Server 2005, this failure
> may be caused by the fact that under the default settings SQL Server does not
> allow remote connections. (provider: Named Pipes Provider, error: 40 - Could
> not open a connection to SQL Server)
> Can someone help me with this? I have both tcp/ip and named pipes enabled.
> --
> Thanks|||The connections string is:
Cn = new SqlConnection("Network=DBMSSOCN;Data Source=192.168.1.103;Initial
Catalog=sqlexpress;Integrated Security=SSPI");
The new error message I get is:
(provider: TCP Provider, error: 0 - No connection could be made because the
target machine actively refused it.)
The detail is as follows:
System.Data.SqlClient.SqlException: An error has occurred while establishing
a connection to the server. When connecting to SQL Server 2005, this failure
may be caused by the fact that under the default settings SQL Server does not
allow remote connections. (provider: TCP Provider, error: 0 - No connection
could be made because the target machine actively refused it.)
It appears that the connection is blocked but I'm not sure where. I've
checked Windows Firewall and made sure that the appropriate ports are open...
--
Thanks
"Ryan Powers" wrote:
> Can you post your connection string?
> specifying
> Network=DBMSSOCN
> in your connection string will cause it to use tcp instead of named pipes,
> which is less error prone.
> See here for more details:
> http://www.aspfaq.com/show.asp?id=2126
> Also, check out the post regarding connections to sql express.
> http://www.aspfaq.com/sql2005/show.asp?id=3
> HTH
> --
> Ryan Powers
> Clarity Consulting
> http://www.claritycon.com
>
> "Greg" wrote:
> > Ok,
> >
> > I've spent a bunch of hours trying to figure out how to connect to SQL
> > Server 2005. I have MSDE 2005, IIS 6.0 and ASP.NET configured on my laptop.
> > I can run ASP.net code with no problem. I can access SQL Server from the
> > command line using osql with no problem.
> >
> > But trying to access sql server 2005 from asp.net yields the following
> > message:
> >
> > System.Data.SqlClient.SqlException: An error has occurred while establishing
> > a connection to the server. When connecting to SQL Server 2005, this failure
> > may be caused by the fact that under the default settings SQL Server does not
> > allow remote connections. (provider: Named Pipes Provider, error: 40 - Could
> > not open a connection to SQL Server)
> >
> > Can someone help me with this? I have both tcp/ip and named pipes enabled.
> >
> > --
> > Thanks|||Check out this link.
http://blogs.msdn.com/sqlexpress/archive/2005/05/05/415084.aspx
This is a post that explains exactly how to enable remote connections for
express.
Ryan Powers
Clarity Consulting
http://www.claritycon.com
"Greg" wrote:
> The connections string is:
> Cn = new SqlConnection("Network=DBMSSOCN;Data Source=192.168.1.103;Initial
> Catalog=sqlexpress;Integrated Security=SSPI");
> The new error message I get is:
> (provider: TCP Provider, error: 0 - No connection could be made because the
> target machine actively refused it.)
> The detail is as follows:
> System.Data.SqlClient.SqlException: An error has occurred while establishing
> a connection to the server. When connecting to SQL Server 2005, this failure
> may be caused by the fact that under the default settings SQL Server does not
> allow remote connections. (provider: TCP Provider, error: 0 - No connection
> could be made because the target machine actively refused it.)
> It appears that the connection is blocked but I'm not sure where. I've
> checked Windows Firewall and made sure that the appropriate ports are open...
> --
> Thanks
>
> "Ryan Powers" wrote:
> > Can you post your connection string?
> >
> > specifying
> > Network=DBMSSOCN
> > in your connection string will cause it to use tcp instead of named pipes,
> > which is less error prone.
> >
> > See here for more details:
> > http://www.aspfaq.com/show.asp?id=2126
> >
> > Also, check out the post regarding connections to sql express.
> > http://www.aspfaq.com/sql2005/show.asp?id=3
> >
> > HTH
> >
> > --
> > Ryan Powers
> > Clarity Consulting
> > http://www.claritycon.com
> >
> >
> > "Greg" wrote:
> >
> > > Ok,
> > >
> > > I've spent a bunch of hours trying to figure out how to connect to SQL
> > > Server 2005. I have MSDE 2005, IIS 6.0 and ASP.NET configured on my laptop.
> > > I can run ASP.net code with no problem. I can access SQL Server from the
> > > command line using osql with no problem.
> > >
> > > But trying to access sql server 2005 from asp.net yields the following
> > > message:
> > >
> > > System.Data.SqlClient.SqlException: An error has occurred while establishing
> > > a connection to the server. When connecting to SQL Server 2005, this failure
> > > may be caused by the fact that under the default settings SQL Server does not
> > > allow remote connections. (provider: Named Pipes Provider, error: 40 - Could
> > > not open a connection to SQL Server)
> > >
> > > Can someone help me with this? I have both tcp/ip and named pipes enabled.
> > >
> > > --
> > > Thanks|||Excellent! I had to change from dynamic to static TCP port number. It works
great now.
Thanks for all your help
Greg
"Ryan Powers" wrote:
> Check out this link.
> http://blogs.msdn.com/sqlexpress/archive/2005/05/05/415084.aspx
> This is a post that explains exactly how to enable remote connections for
> express.
>
> --
> Ryan Powers
> Clarity Consulting
> http://www.claritycon.com
>
> "Greg" wrote:
> > The connections string is:
> > Cn = new SqlConnection("Network=DBMSSOCN;Data Source=192.168.1.103;Initial
> > Catalog=sqlexpress;Integrated Security=SSPI");
> >
> > The new error message I get is:
> > (provider: TCP Provider, error: 0 - No connection could be made because the
> > target machine actively refused it.)
> >
> > The detail is as follows:
> > System.Data.SqlClient.SqlException: An error has occurred while establishing
> > a connection to the server. When connecting to SQL Server 2005, this failure
> > may be caused by the fact that under the default settings SQL Server does not
> > allow remote connections. (provider: TCP Provider, error: 0 - No connection
> > could be made because the target machine actively refused it.)
> >
> > It appears that the connection is blocked but I'm not sure where. I've
> > checked Windows Firewall and made sure that the appropriate ports are open...
> >
> > --
> > Thanks
> >
> >
> > "Ryan Powers" wrote:
> >
> > > Can you post your connection string?
> > >
> > > specifying
> > > Network=DBMSSOCN
> > > in your connection string will cause it to use tcp instead of named pipes,
> > > which is less error prone.
> > >
> > > See here for more details:
> > > http://www.aspfaq.com/show.asp?id=2126
> > >
> > > Also, check out the post regarding connections to sql express.
> > > http://www.aspfaq.com/sql2005/show.asp?id=3
> > >
> > > HTH
> > >
> > > --
> > > Ryan Powers
> > > Clarity Consulting
> > > http://www.claritycon.com
> > >
> > >
> > > "Greg" wrote:
> > >
> > > > Ok,
> > > >
> > > > I've spent a bunch of hours trying to figure out how to connect to SQL
> > > > Server 2005. I have MSDE 2005, IIS 6.0 and ASP.NET configured on my laptop.
> > > > I can run ASP.net code with no problem. I can access SQL Server from the
> > > > command line using osql with no problem.
> > > >
> > > > But trying to access sql server 2005 from asp.net yields the following
> > > > message:
> > > >
> > > > System.Data.SqlClient.SqlException: An error has occurred while establishing
> > > > a connection to the server. When connecting to SQL Server 2005, this failure
> > > > may be caused by the fact that under the default settings SQL Server does not
> > > > allow remote connections. (provider: Named Pipes Provider, error: 40 - Could
> > > > not open a connection to SQL Server)
> > > >
> > > > Can someone help me with this? I have both tcp/ip and named pipes enabled.
> > > >
> > > > --
> > > > Thanks

Named instance, no default instance -> connection problems?

Hey,
I have the following problem with deployment of MSDE. Here's what I want
to do:
- I want to install MSDE in a named instance, even if it wasn't installed
before.
- I want to connect to the local server only, if possible with a
"generic" name, so I don't have to look up the system name
and stuff.
I can't really get this to work at all. I have connection strings that
work fine on development machines (where the default instance name is
used), using . for the server name. On the test machine, using
..\MYINSTANCE doesn't work at all. I read suggestions to use
(local)\MYINSTANCE instead of .\MYINSTANCE, but to no avail.
The funny thing is, even SYSTEMNAME\MYINSTANCE doesn't work unless there's
a default instance running on the same machine. Plus, it seems cumbersome
to have to find out the system's name for such a purpose.
Maybe I'm just seriously wrong about something... I didn't think it would
be that hard to set up a local (!, no networking enabled) database server
using the standard (!, they do say I'm to use a vendor-specific instance,
don't they?) setup procedure and connect to that.
Any ideas, please?
Oliver Sturm
omnibus ex nihilo ducendis sufficit unum
MSN oliver@.sturmnet.org Jabber sturm@.amessage.de ICQ 27142619
hi Oliver,
"Oliver Sturm" <oliver@.sturmnet.org> ha scritto nel messaggio
news:pan.2004.06.18.10.39.55.285051@.sturmnet.org.. .
> Hey,
> I have the following problem with deployment of MSDE. Here's what I want
> to do:
> - I want to install MSDE in a named instance, even if it wasn't installed
> before.
> - I want to connect to the local server only, if possible with a
> "generic" name, so I don't have to look up the system name
> and stuff.
> I can't really get this to work at all. I have connection strings that
> work fine on development machines (where the default instance name is
> used), using . for the server name. On the test machine, using
> .\MYINSTANCE doesn't work at all. I read suggestions to use
> (local)\MYINSTANCE instead of .\MYINSTANCE, but to no avail.
> The funny thing is, even SYSTEMNAME\MYINSTANCE doesn't work unless there's
> a default instance running on the same machine. Plus, it seems cumbersome
> to have to find out the system's name for such a purpose.
> Maybe I'm just seriously wrong about something... I didn't think it would
> be that hard to set up a local (!, no networking enabled) database server
> using the standard (!, they do say I'm to use a vendor-specific instance,
> don't they?) setup procedure and connect to that.
> Any ideas, please?
that's weird, becouse (local)\InstanceName shoul'd be fine..... ok, I'm
running a pc with a default instance and a named instance...
as regard the ComputerName part, remember you are trying to connect to a
service specified on the target pc...
you can always set an Alias via Client Network Utility, but this is not the
case... but building the connection string using something similar to Public
Declare Function GetComputerName Lib "kernel32" Alias "GetComputerNameA"
(ByVal lpBuffer As String, nSize As Long) As Long, appending the
"\YourInstanceName", in your preferred language, coul'd solve the problem
too...
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
sql

Named Instance, Connectivity Question

I had XP Machine, with SQL Server 2000 Client
preinstalled.
This week, I installed MSDE 2000 under Named Instance.
After this, I restart my PC, I can see the Names Instance
is up running under Service window.
By My SQL server Enterprise Manager and SQL Analyzer wont
see the instance or any MSDE server.
Then I installed default Instance(no name), then
Enterprise Manager and SQL Analyzer can see MSDE sever
under LOCAL name, I assume this is the default instance.
My VB Data Enviroment can see a MSDE server under my
Computer name.
My Questiona are:
1. How do I login the named instance?
2. can I installed Named instance alone without a default
instance? if not, does the install sequence matters?
3. how to rollback my installation in case I want retry?
Greg Chang
hi Greg,
"Greg Chang" <anonymous@.discussions.microsoft.com> ha scritto nel messaggio
news:176dc01c418d4$3cb51410$a501280a@.phx.gbl...
> I had XP Machine, with SQL Server 2000 Client
> preinstalled.
> This week, I installed MSDE 2000 under Named Instance.
> After this, I restart my PC, I can see the Names Instance
> is up running under Service window.
> By My SQL server Enterprise Manager and SQL Analyzer wont
> see the instance or any MSDE server.
> Then I installed default Instance(no name), then
> Enterprise Manager and SQL Analyzer can see MSDE sever
> under LOCAL name, I assume this is the default instance.
> My VB Data Enviroment can see a MSDE server under my
> Computer name.
thi can be due to
http://support.microsoft.com/default...b;EN-US;814132 ...
there are other undocumented issues regarding instance names not showing up
in the service manager list thought...

> My Questiona are:
> 1. How do I login the named instance?
you must provide the full name as ComputerName\InstanceName

> 2. can I installed Named instance alone without a default
> instance? if not, does the install sequence matters?
yes, you can install only a named instance, only a default instance, or upt
to 15 named instances and 1 default instance...

> 3. how to rollback my installation in case I want retry?
you have to fully uninstall it... go in control panel and use the
install/uninstall applet...
hth
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.7.0 - DbaMgr ver 0.53.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

Named Instance Not Visible local instance visible but does not exist?!?!

I have installed a named instance of MSDE on 4 machines with no problems.
Some had preexisting versions of local which were uninstalled no problems.
On this machine the local instance has been uninstalled. The names instance
installs fine however when you try to connect the named instances are not
visible but the now non existing local instance is visible. Connecting to
ether by manually typing in computername\instancename does not work. I have
removed folders registry values ect with no luck. Any Ideas?
Shane Lim
hi Shane,
"Shane Lim" <gslim@.spatialdynamics.com> ha scritto nel messaggio
news:%23opqoD84EHA.2180@.TK2MSFTNGP10.phx.gbl
> I have installed a named instance of MSDE on 4 machines with no
> problems. Some had preexisting versions of local which were
> uninstalled no problems. On this machine the local instance has been
> uninstalled. The names instance installs fine however when you try to
> connect the named instances are not visible but the now non existing
> local instance is visible. Connecting to ether by manually typing in
> computername\instancename does not work. I have removed folders
> registry values ect with no luck. Any Ideas?
> Shane Lim
what (SQL Server) service name is available in the Control
Panel->management->Services applet?
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||I only have the MSQL&Instancename and the SQLAGENT$instancename.
They are both set to log in with the localmachine administrator.
When I try to conntect with query analyzer it doesn't show up in the
list but just the computername does. When I type in the
computername/instancename it says connecting then after a bit I get
undable to connect to server computername\instancename:
Server:Msg17,level16, State 1
[Microsoft][ODBC SQL Server Driver][DBNETLIB]Sql Server does not exist
or Access is denied.
Same thing when I just click on the computername that is in the list
of available servers after I click the refresh button.
If I uninstall everything then the computername is not available. But
once I reinstall an instance its back.
I even removed all the SQL server Registry enteries under local
machine > software > microsoft still no luck.
On Fri, 17 Dec 2004 12:16:37 +0100, "Andrea Montanari"
<andrea.sqlDMO@.virgilio.it> wrote:

>hi Shane,
>"Shane Lim" <gslim@.spatialdynamics.com> ha scritto nel messaggio
>news:%23opqoD84EHA.2180@.TK2MSFTNGP10.phx.gbl
>what (SQL Server) service name is available in the Control
>Panel->management->Services applet?
|||hi Shane,
"Shane Lim" <gslim@.blizzardice.com> ha scritto nel messaggio
news:fs66s09089a0igajttiku8q93r7stnrj4h@.4ax.com
> ...
> Server:Msg17,level16, State 1
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]Sql Server does not exist
> or Access is denied.
please have a look at
http://support.microsoft.com/default...06&Product=sql
for potential causes of this problem..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

Named Instance naming rules

Hi, I'm trying to wrap the MSDE command line installer with an
InstallShield setup. One of the requirements is that the user can choose to
install a named instance and can choose the name of the named instance.
Here's what I found on SQL BOL:
"A new instance name must begin with a letter, an ampersand (&), or an
underscore (_), and can contain numbers, letters, or other characters. SQL
Server sysnames and reserved names should not be used as instance names. For
example, the term "default" should not be used as an instance name because
it is a reserved name used by Setup."
That's a little vague for trying to write an installer. Does anyone know the
specific rules for a naming a named instance? For example - how long can the
name be? can there be spaces in the name? what exactly are "other
characters" - anything?Refer "Instance Name" under "instance names" in BOL
--
Thanks
Ravi
"Andy Gaskell" wrote:
> Hi, I'm trying to wrap the MSDE command line installer with an
> InstallShield setup. One of the requirements is that the user can choose to
> install a named instance and can choose the name of the named instance.
> Here's what I found on SQL BOL:
> "A new instance name must begin with a letter, an ampersand (&), or an
> underscore (_), and can contain numbers, letters, or other characters. SQL
> Server sysnames and reserved names should not be used as instance names. For
> example, the term "default" should not be used as an instance name because
> it is a reserved name used by Setup."
> That's a little vague for trying to write an installer. Does anyone know the
> specific rules for a naming a named instance? For example - how long can the
> name be? can there be spaces in the name? what exactly are "other
> characters" - anything?
>
>|||Thanks Ravi.
"Ravi" <Ravi@.discussions.microsoft.com> wrote in message
news:AAC8D56C-739C-4C63-8EC2-AABF3937382F@.microsoft.com...
> Refer "Instance Name" under "instance names" in BOL
> --
> Thanks
> Ravi
>
> "Andy Gaskell" wrote:
>> Hi, I'm trying to wrap the MSDE command line installer with an
>> InstallShield setup. One of the requirements is that the user can choose
>> to
>> install a named instance and can choose the name of the named instance.
>> Here's what I found on SQL BOL:
>> "A new instance name must begin with a letter, an ampersand (&), or an
>> underscore (_), and can contain numbers, letters, or other characters.
>> SQL
>> Server sysnames and reserved names should not be used as instance names.
>> For
>> example, the term "default" should not be used as an instance name
>> because
>> it is a reserved name used by Setup."
>> That's a little vague for trying to write an installer. Does anyone know
>> the
>> specific rules for a naming a named instance? For example - how long can
>> the
>> name be? can there be spaces in the name? what exactly are "other
>> characters" - anything?
>>

Named Instance naming rules

Hi, I'm trying to wrap the MSDE command line installer with an
InstallShield setup. One of the requirements is that the user can choose to
install a named instance and can choose the name of the named instance.
Here's what I found on SQL BOL:
"A new instance name must begin with a letter, an ampersand (&), or an
underscore (_), and can contain numbers, letters, or other characters. SQL
Server sysnames and reserved names should not be used as instance names. For
example, the term "default" should not be used as an instance name because
it is a reserved name used by Setup."
That's a little vague for trying to write an installer. Does anyone know the
specific rules for a naming a named instance? For example - how long can the
name be? can there be spaces in the name? what exactly are "other
characters" - anything?Refer "Instance Name" under "instance names" in BOL
--
Thanks
Ravi
"Andy Gaskell" wrote:

> Hi, I'm trying to wrap the MSDE command line installer with an
> InstallShield setup. One of the requirements is that the user can choose t
o
> install a named instance and can choose the name of the named instance.
> Here's what I found on SQL BOL:
> "A new instance name must begin with a letter, an ampersand (&), or an
> underscore (_), and can contain numbers, letters, or other characters. SQL
> Server sysnames and reserved names should not be used as instance names. F
or
> example, the term "default" should not be used as an instance name because
> it is a reserved name used by Setup."
> That's a little vague for trying to write an installer. Does anyone know t
he
> specific rules for a naming a named instance? For example - how long can t
he
> name be? can there be spaces in the name? what exactly are "other
> characters" - anything?
>
>|||Thanks Ravi.
"Ravi" <Ravi@.discussions.microsoft.com> wrote in message
news:AAC8D56C-739C-4C63-8EC2-AABF3937382F@.microsoft.com...[vbcol=seagreen]
> Refer "Instance Name" under "instance names" in BOL
> --
> Thanks
> Ravi
>
> "Andy Gaskell" wrote:
>sql

Named Instance naming rules

Hi, I'm trying to wrap the MSDE command line installer with an
InstallShield setup. One of the requirements is that the user can choose to
install a named instance and can choose the name of the named instance.
Here's what I found on SQL BOL:
"A new instance name must begin with a letter, an ampersand (&), or an
underscore (_), and can contain numbers, letters, or other characters. SQL
Server sysnames and reserved names should not be used as instance names. For
example, the term "default" should not be used as an instance name because
it is a reserved name used by Setup."
That's a little vague for trying to write an installer. Does anyone know the
specific rules for a naming a named instance? For example - how long can the
name be? can there be spaces in the name? what exactly are "other
characters" - anything?
Refer "Instance Name" under "instance names" in BOL
Thanks
Ravi
"Andy Gaskell" wrote:

> Hi, I'm trying to wrap the MSDE command line installer with an
> InstallShield setup. One of the requirements is that the user can choose to
> install a named instance and can choose the name of the named instance.
> Here's what I found on SQL BOL:
> "A new instance name must begin with a letter, an ampersand (&), or an
> underscore (_), and can contain numbers, letters, or other characters. SQL
> Server sysnames and reserved names should not be used as instance names. For
> example, the term "default" should not be used as an instance name because
> it is a reserved name used by Setup."
> That's a little vague for trying to write an installer. Does anyone know the
> specific rules for a naming a named instance? For example - how long can the
> name be? can there be spaces in the name? what exactly are "other
> characters" - anything?
>
>
|||Thanks Ravi.
"Ravi" <Ravi@.discussions.microsoft.com> wrote in message
news:AAC8D56C-739C-4C63-8EC2-AABF3937382F@.microsoft.com...[vbcol=seagreen]
> Refer "Instance Name" under "instance names" in BOL
> --
> Thanks
> Ravi
>
> "Andy Gaskell" wrote:

Named instance connection problem

Have an MSDE named instance which works just fine. Just installed
another instance of the same and can only connect to it using OSQL
locally, nothing across the network. I made sure to use all the
gotcha flags during install to enable network access, etc:
setup.exe DISABLENETWORKPROTOCOLS=0 SAPWD="sapassword"
INSTANCENAME="instancename" SECURITYMODE=SQL /L*v
c:\temp\msdeinstlog.txt
After the install and reboot, also verified that network access is
allowed using SVRNETCN, where both named pipes and TCP connections are
enabled.
Tried connecting using "sa" and trusted NT auth and both work locally,
but across the network it's always:
[DBNETLIB]SQL Server does not exist or access denied.
[DBNETLIB]ConnectionOpen (Connect()).
No firewalls in the way from client to server. As a matter of fact,
when I telnet to the TCP port shown in SVRNETCN, the connection is
established, so the port is obviously open.
I'm racking my brain on this one... What gives?
Thanks guys,
-Peter.
Peter Lecki wrote:
> Have an MSDE named instance which works just fine. Just installed
> another instance of the same and can only connect to it using OSQL
> locally, nothing across the network. I made sure to use all the
> gotcha flags during install to enable network access, etc:
> setup.exe DISABLENETWORKPROTOCOLS=0 SAPWD="sapassword"
> INSTANCENAME="instancename" SECURITYMODE=SQL /L*v
> c:\temp\msdeinstlog.txt
> After the install and reboot, also verified that network access is
> allowed using SVRNETCN, where both named pipes and TCP connections are
> enabled.
> Tried connecting using "sa" and trusted NT auth and both work locally,
> but across the network it's always:
> [DBNETLIB]SQL Server does not exist or access denied.
> [DBNETLIB]ConnectionOpen (Connect()).
> No firewalls in the way from client to server. As a matter of fact,
> when I telnet to the TCP port shown in SVRNETCN, the connection is
> established, so the port is obviously open.
> I'm racking my brain on this one... What gives?
> Thanks guys,
> -Peter.
Starting with SQL Server Desktop Engine (also known as MSDE 2000)
Service Pack 3 (SP3) or SP3a , only local connectivity is permitted, by
default. If you want to permit remote connections to SQL Server Desktop
Engine, follow the steps in the following article:
814130 (http://support.microsoft.com/kb/814130/) How to help secure
network connectivity for SQL Server 2000 local databases
http://support.microsoft.com/kb/814130/
David Gugick
Quest Software
www.quest.com

Named instance connection problem

Have an MSDE named instance which works just fine. Just installed
another instance of the same and can only connect to it using OSQL
locally, nothing across the network. I made sure to use all the
gotcha flags during install to enable network access, etc:
setup.exe DISABLENETWORKPROTOCOLS=0 SAPWD="sapassword"
INSTANCENAME="instancename" SECURITYMODE=SQL /L*v
c:\temp\msdeinstlog.txt
After the install and reboot, also verified that network access is
allowed using SVRNETCN, where both named pipes and TCP connections are
enabled.
Tried connecting using "sa" and trusted NT auth and both work locally,
but across the network it's always:
[DBNETLIB]SQL Server does not exist or access denied.
[DBNETLIB]ConnectionOpen (Connect()).
No firewalls in the way from client to server. As a matter of fact,
when I telnet to the TCP port shown in SVRNETCN, the connection is
established, so the port is obviously open.
I'm racking my brain on this one... What gives?
Thanks guys,
-Peter.
Peter Lecki wrote:
> Have an MSDE named instance which works just fine. Just installed
> another instance of the same and can only connect to it using OSQL
> locally, nothing across the network. I made sure to use all the
> gotcha flags during install to enable network access, etc:
> setup.exe DISABLENETWORKPROTOCOLS=0 SAPWD="sapassword"
> INSTANCENAME="instancename" SECURITYMODE=SQL /L*v
> c:\temp\msdeinstlog.txt
> After the install and reboot, also verified that network access is
> allowed using SVRNETCN, where both named pipes and TCP connections are
> enabled.
> Tried connecting using "sa" and trusted NT auth and both work locally,
> but across the network it's always:
> [DBNETLIB]SQL Server does not exist or access denied.
> [DBNETLIB]ConnectionOpen (Connect()).
> No firewalls in the way from client to server. As a matter of fact,
> when I telnet to the TCP port shown in SVRNETCN, the connection is
> established, so the port is obviously open.
> I'm racking my brain on this one... What gives?
> Thanks guys,
> -Peter.
Starting with SQL Server Desktop Engine (also known as MSDE 2000)
Service Pack 3 (SP3) or SP3a , only local connectivity is permitted, by
default. If you want to permit remote connections to SQL Server Desktop
Engine, follow the steps in the following article:
814130 (http://support.microsoft.com/kb/814130/) How to help secure
network connectivity for SQL Server 2000 local databases
http://support.microsoft.com/kb/814130/
David Gugick
Quest Software
www.quest.com

Named instance connection problem

Have an MSDE named instance which works just fine. Just installed
another instance of the same and can only connect to it using OSQL
locally, nothing across the network. I made sure to use all the
gotcha flags during install to enable network access, etc:
setup.exe DISABLENETWORKPROTOCOLS=0 SAPWD="sapassword"
INSTANCENAME="instancename" SECURITYMODE=SQL /L*v
c:\temp\msdeinstlog.txt
After the install and reboot, also verified that network access is
allowed using SVRNETCN, where both named pipes and TCP connections are
enabled.
Tried connecting using "sa" and trusted NT auth and both work locally,
but across the network it's always:
[DBNETLIB]SQL Server does not exist or access denied.
[DBNETLIB]ConnectionOpen (Connect()).
No firewalls in the way from client to server. As a matter of fact,
when I telnet to the TCP port shown in SVRNETCN, the connection is
established, so the port is obviously open.
I'm racking my brain on this one... What gives?
Thanks guys,
-Peter.Peter Lecki wrote:
> Have an MSDE named instance which works just fine. Just installed
> another instance of the same and can only connect to it using OSQL
> locally, nothing across the network. I made sure to use all the
> gotcha flags during install to enable network access, etc:
> setup.exe DISABLENETWORKPROTOCOLS=0 SAPWD="sapassword"
> INSTANCENAME="instancename" SECURITYMODE=SQL /L*v
> c:\temp\msdeinstlog.txt
> After the install and reboot, also verified that network access is
> allowed using SVRNETCN, where both named pipes and TCP connections are
> enabled.
> Tried connecting using "sa" and trusted NT auth and both work locally,
> but across the network it's always:
> [DBNETLIB]SQL Server does not exist or access denied.
> [DBNETLIB]ConnectionOpen (Connect()).
> No firewalls in the way from client to server. As a matter of fact,
> when I telnet to the TCP port shown in SVRNETCN, the connection is
> established, so the port is obviously open.
> I'm racking my brain on this one... What gives?
> Thanks guys,
> -Peter.
Starting with SQL Server Desktop Engine (also known as MSDE 2000)
Service Pack 3 (SP3) or SP3a , only local connectivity is permitted, by
default. If you want to permit remote connections to SQL Server Desktop
Engine, follow the steps in the following article:
814130 (http://support.microsoft.com/kb/814130/) How to help secure
network connectivity for SQL Server 2000 local databases
http://support.microsoft.com/kb/814130/
--
David Gugick
Quest Software
www.quest.comsql

Named instance connection problem

Have an MSDE named instance which works just fine. Just installed
another instance of the same and can only connect to it using OSQL
locally, nothing across the network. I made sure to use all the
gotcha flags during install to enable network access, etc:
setup.exe DISABLENETWORKPROTOCOLS=0 SAPWD="sapassword"
INSTANCENAME="instancename" SECURITYMODE=SQL /L*v
c:\temp\msdeinstlog.txt
After the install and reboot, also verified that network access is
allowed using SVRNETCN, where both named pipes and TCP connections are
enabled.
Tried connecting using "sa" and trusted NT auth and both work locally,
but across the network it's always:
[DBNETLIB]SQL Server does not exist or access denied.
[DBNETLIB]ConnectionOpen (Connect()).
No firewalls in the way from client to server. As a matter of fact,
when I telnet to the TCP port shown in SVRNETCN, the connection is
established, so the port is obviously open.
I'm racking my brain on this one... What gives?
Thanks guys,
-Peter.Peter Lecki wrote:
> Have an MSDE named instance which works just fine. Just installed
> another instance of the same and can only connect to it using OSQL
> locally, nothing across the network. I made sure to use all the
> gotcha flags during install to enable network access, etc:
> setup.exe DISABLENETWORKPROTOCOLS=0 SAPWD="sapassword"
> INSTANCENAME="instancename" SECURITYMODE=SQL /L*v
> c:\temp\msdeinstlog.txt
> After the install and reboot, also verified that network access is
> allowed using SVRNETCN, where both named pipes and TCP connections are
> enabled.
> Tried connecting using "sa" and trusted NT auth and both work locally,
> but across the network it's always:
> [DBNETLIB]SQL Server does not exist or access denied.
> [DBNETLIB]ConnectionOpen (Connect()).
> No firewalls in the way from client to server. As a matter of fact,
> when I telnet to the TCP port shown in SVRNETCN, the connection is
> established, so the port is obviously open.
> I'm racking my brain on this one... What gives?
> Thanks guys,
> -Peter.
Starting with SQL Server Desktop Engine (also known as MSDE 2000)
Service Pack 3 (SP3) or SP3a , only local connectivity is permitted, by
default. If you want to permit remote connections to SQL Server Desktop
Engine, follow the steps in the following article:
814130 (http://support.microsoft.com/kb/814130/) How to help secure
network connectivity for SQL Server 2000 local databases
http://support.microsoft.com/kb/814130/
David Gugick
Quest Software
www.quest.com

Named instance connection problem

Have an MSDE named instance which works just fine. Just installed
another instance of the same and can only connect to it using OSQL
locally, nothing across the network. I made sure to use all the
gotcha flags during install to enable network access, etc:
setup.exe DISABLENETWORKPROTOCOLS=0 SAPWD="sapassword"
INSTANCENAME="instancename" SECURITYMODE=SQL /L*v
c:\temp\msdeinstlog.txt
After the install and reboot, also verified that network access is
allowed using SVRNETCN, where both named pipes and TCP connections are
enabled.
Tried connecting using "sa" and trusted NT auth and both work locally,
but across the network it's always:
[DBNETLIB]SQL Server does not exist or access denied.
[DBNETLIB]ConnectionOpen (Connect()).
No firewalls in the way from client to server. As a matter of fact,
when I telnet to the TCP port shown in SVRNETCN, the connection is
established, so the port is obviously open.
I'm racking my brain on this one... What gives?
Thanks guys,
-Peter.
Peter Lecki wrote:
> Have an MSDE named instance which works just fine. Just installed
> another instance of the same and can only connect to it using OSQL
> locally, nothing across the network. I made sure to use all the
> gotcha flags during install to enable network access, etc:
> setup.exe DISABLENETWORKPROTOCOLS=0 SAPWD="sapassword"
> INSTANCENAME="instancename" SECURITYMODE=SQL /L*v
> c:\temp\msdeinstlog.txt
> After the install and reboot, also verified that network access is
> allowed using SVRNETCN, where both named pipes and TCP connections are
> enabled.
> Tried connecting using "sa" and trusted NT auth and both work locally,
> but across the network it's always:
> [DBNETLIB]SQL Server does not exist or access denied.
> [DBNETLIB]ConnectionOpen (Connect()).
> No firewalls in the way from client to server. As a matter of fact,
> when I telnet to the TCP port shown in SVRNETCN, the connection is
> established, so the port is obviously open.
> I'm racking my brain on this one... What gives?
> Thanks guys,
> -Peter.
Starting with SQL Server Desktop Engine (also known as MSDE 2000)
Service Pack 3 (SP3) or SP3a , only local connectivity is permitted, by
default. If you want to permit remote connections to SQL Server Desktop
Engine, follow the steps in the following article:
814130 (http://support.microsoft.com/kb/814130/) How to help secure
network connectivity for SQL Server 2000 local databases
http://support.microsoft.com/kb/814130/
David Gugick
Quest Software
www.quest.com

Named instance connection problem

Have an MSDE named instance which works just fine. Just installed
another instance of the same and can only connect to it using OSQL
locally, nothing across the network. I made sure to use all the
gotcha flags during install to enable network access, etc:
setup.exe DISABLENETWORKPROTOCOLS=0 SAPWD="sapassword"
INSTANCENAME="instancename" SECURITYMODE=SQL /L*v
c:\temp\msdeinstlog.txt
After the install and reboot, also verified that network access is
allowed using SVRNETCN, where both named pipes and TCP connections are
enabled.
Tried connecting using "sa" and trusted NT auth and both work locally,
but across the network it's always:
[DBNETLIB]SQL Server does not exist or access denied.
[DBNETLIB]ConnectionOpen (Connect()).
No firewalls in the way from client to server. As a matter of fact,
when I telnet to the TCP port shown in SVRNETCN, the connection is
established, so the port is obviously open.
I'm racking my brain on this one... What gives?
Thanks guys,
-Peter.
Peter Lecki wrote:
> Have an MSDE named instance which works just fine. Just installed
> another instance of the same and can only connect to it using OSQL
> locally, nothing across the network. I made sure to use all the
> gotcha flags during install to enable network access, etc:
> setup.exe DISABLENETWORKPROTOCOLS=0 SAPWD="sapassword"
> INSTANCENAME="instancename" SECURITYMODE=SQL /L*v
> c:\temp\msdeinstlog.txt
> After the install and reboot, also verified that network access is
> allowed using SVRNETCN, where both named pipes and TCP connections are
> enabled.
> Tried connecting using "sa" and trusted NT auth and both work locally,
> but across the network it's always:
> [DBNETLIB]SQL Server does not exist or access denied.
> [DBNETLIB]ConnectionOpen (Connect()).
> No firewalls in the way from client to server. As a matter of fact,
> when I telnet to the TCP port shown in SVRNETCN, the connection is
> established, so the port is obviously open.
> I'm racking my brain on this one... What gives?
> Thanks guys,
> -Peter.
Starting with SQL Server Desktop Engine (also known as MSDE 2000)
Service Pack 3 (SP3) or SP3a , only local connectivity is permitted, by
default. If you want to permit remote connections to SQL Server Desktop
Engine, follow the steps in the following article:
814130 (http://support.microsoft.com/kb/814130/) How to help secure
network connectivity for SQL Server 2000 local databases
http://support.microsoft.com/kb/814130/
David Gugick
Quest Software
www.quest.com

n00b Question Re: MSDE SQL Server Install

I am trying to install some code on my website which is called EasyDisk. It
creates a forum, like any forum you see anywhere. Anyways it requires an SQL
Server, so I acquired MSDE SQL Server 2000. I created an instance of it, and
can see the folder on my C drive. The instance is called
MYFIRSTDBMSSQL$MYFIRSTDB oddly enough since I guess I didn't understand the
instruction for naming an instance. In any case, the forum software requires
I know 1. The name of my SQL Server, 2. My username 3. My password and 4. My
database name.
So, best I can tell my db name is my instance name, and my username and
password are what I use to log onto Windows XP. How far off am I? ... and I
have no idea what my sql server name is. How do I find out? The Books online
is no help whatsoever in this regard.
Thanks,
Jim
hi Jim,
"newgenre" <newgenre@.mindspring.com> ha scritto nel messaggio
news:%xchc.3922$e4.2441@.newsread2.news.pas.earthli nk.net...
>.....
> I know 1. The name of my SQL Server, 2. My username 3. My password and 4.
My
> database name.
> So, best I can tell my db name is my instance name, and my username and
> password are what I use to log onto Windows XP. How far off am I? ... and
I
> have no idea what my sql server name is. How do I find out? The Books
online
> is no help whatsoever in this regard.
your instance name shoul'd be MYFIRSTDB (and you can verify this opening
your service management applet, in the part right to the $ sign)... the
service manager in your tray bar area shoul'd provide this information
too...
so the full instance name is YourComputerName\MYFIRSTDB
your db name for the connection string is not the instance name, but the
database you want to connect to..
as regard your credential, it depends on the authentication mode you want to
connect to SQL Server with..
SQL Server accepst 2 kinds of authentication mode:
trusted (WinNT) authentication, where you are not required to provide user's
information;
SQL Server authentication, where you have to provide them in the form of
"user id=username;password=yourStrongPwd;" as indicated in
http://www.connectionstrings.com/ ...
you can find more about authentication modes beginning at
http://msdn.microsoft.com/library/de...setup_6p9v.asp
you can find which kind of authentication your MSDE instance supports by
inspecting the registry at the
HKLM\Software\Microsoft\Microsoft SQL
Server\YourInstanceName\MSSQLServer\LoginMode key
a value of 0 or 2 specifies Mixed mode (both modes), while a value of 1
spefies truste authentication only.
hth
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.7.0 - DbaMgr ver 0.53.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
sql

n00b Question Re: MSDE SQL Server Install

Sorry if I sound to simple for you, I'm not sure what your
experience is, and this is how I understand it best.)
SQL Server runs as a Service. That's an app that runs in
the background.
You can have more that one 'Instance' of SQL Server
running at a time. (The number allowed depends on the
version you install.) This allows, let's say, your Website
database running in one instance to crash without having
your accounting db (on another instance) going down also.
On each instance of SQL Server, you can have a number of
Databases.
Hopes that clears some things up. Did you install MSDE (MS
SQL Server Desktop Edition) or SQL Server
Standard/Enterprise/Personal edition?
MSDE does not install some management tools that make
things real easy.
It was Desktop Edition.
"M K" <mark@.nospamcenturycolor.com> wrote in message
news:252001c427c3$54b21740$a001280a@.phx.gbl...
> Sorry if I sound to simple for you, I'm not sure what your
> experience is, and this is how I understand it best.)
> SQL Server runs as a Service. That's an app that runs in
> the background.
> You can have more that one 'Instance' of SQL Server
> running at a time. (The number allowed depends on the
> version you install.) This allows, let's say, your Website
> database running in one instance to crash without having
> your accounting db (on another instance) going down also.
> On each instance of SQL Server, you can have a number of
> Databases.
> Hopes that clears some things up. Did you install MSDE (MS
> SQL Server Desktop Edition) or SQL Server
> Standard/Enterprise/Personal edition?
> MSDE does not install some management tools that make
> things real easy.
|||Yea, Desktop Edition, MSDE, is the redistribution version.
Stripped down. I would think your app would create the
database for itself.
If you don't have a version of SQL running you can install
MSDE with mostly defaults. You don't need to set an
Instance. Then install the app and it should set up the
database.
I hate it when I don't have enough documentation, don't
you.

Mysterious Access Denied Error

Yesterday afternoon I lost access to my local MSDE 2000 sp3(a?)
instance. Usinig NT or SQL authentication I get an 'access denied'
error when I try to connect. This happened suddenly with no changes
to the server on my part. I've tinkered with the Client Network
Utility settings, from Multiprotocol only, every combination of Multi
protocol, TCP/IP, and named pipes. I've tried connecting with my
network machine name, using (local), and using my IP address (both
127.0.0.1 and my network IP). I've tried connecting from Query
Analyzer on other computers. Of course I've rebooted as well, all to
no avail.

I know that there were network changes being made, but my domain login
(which I normally use to connec to my SQL Server as a sysadmin) is
still in the local administrators group on my machine and I haven't
noticed any problems accessing anything else.

Any ideas?MarcosECasa@.yahoo.com (Marcos) wrote in message news:<cf4137bb.0402100934.3c1cc6de@.posting.google.com>...
> Yesterday afternoon I lost access to my local MSDE 2000 sp3(a?)
> instance. Usinig NT or SQL authentication I get an 'access denied'
> error when I try to connect. This happened suddenly with no changes
> to the server on my part. I've tinkered with the Client Network
> Utility settings, from Multiprotocol only, every combination of Multi
> protocol, TCP/IP, and named pipes. I've tried connecting with my
> network machine name, using (local), and using my IP address (both
> 127.0.0.1 and my network IP). I've tried connecting from Query
> Analyzer on other computers. Of course I've rebooted as well, all to
> no avail.
> I know that there were network changes being made, but my domain login
> (which I normally use to connec to my SQL Server as a sysadmin) is
> still in the local administrators group on my machine and I haven't
> noticed any problems accessing anything else.
> Any ideas?

At the risk of asking a silly question, have you checked that the
service is actually running, using NET START for example? If the
service is stopped, then you get the error "SQL Server does not exist
or access denied", whereas if your login is incorrect (security
issue), you would normally get a "Login failed" error instead.

Simon

MySQL compatibility

I have a Windows XP application that uses MSDE as its DB engine. If I
create an identical database in MySQL and include the correct ODBC
"driver", is it be possible to replace MSDE with MySQL?
What does it take for them to be compatible? After all both engines
process SQL commands.
Thanks for any input.
- Alex
"claw" <claw@.hotmail.com> wrote in message
news:2005032101053516807%claw@.hotmailcom...
>I have a Windows XP application that uses MSDE as its DB engine. If I
>create an identical database in MySQL and include the correct ODBC
>"driver", is it be possible to replace MSDE with MySQL?
> What does it take for them to be compatible? After all both engines
> process SQL commands.
> Thanks for any input.
> - Alex
Here's a quote from Google:
<quote>
You will need to use MyOLEDB, MyODBC or the MySQL .NET drivers. All links
given below:
MyOLEDB http://www.mysql.com/portal/siXtes/item-142.html
MyODBC http://www.mysql.com/downloadsX/api-myodbc-3.51.html
MySQL .NET drivers http://sourceforge.net/projectXs/mysqlnet/
I have found that MyODBC gives the most consistent results with .NET,
but others may have had different experiences. I haven't tried the open
source MySQL .NET driver yet, but it looks very promising (and hopefully
speedier than MySQL ODBC).
</quote>
You should also crosscheck data type compatibility.
Peter [MVP Visual Developer]
Jack of all trades, master of none.
|||On Mon, 21 Mar 2005 00:05:35 GMT, claw wrote:

>I have a Windows XP application that uses MSDE as its DB engine. If I
>create an identical database in MySQL and include the correct ODBC
>"driver", is it be possible to replace MSDE with MySQL?
>What does it take for them to be compatible? After all both engines
>process SQL commands.
Hi Alex,
In addition to Peter's reply, here are some other things to consider.
SQL is a highly standardized language. The ANSI standard is based on
SQL-92; the later standards SQL-99 and SQL-2003 (IIRC) are not (yet?)
adopted by ANSI. However, it is entirely up to the manufacturers to
decide to what extend they want to adhere to the standards.
MSDE is quite close to SQL-92 - most, but not all features of SQL-92 are
available. In addition, MSDE also offers a wagonload of proprietary
extra features. While these features can make programs easier to write
and maintain and faster to executed, they will also limit portability.
If the program you are using uses many of these prorietary features,
then it is quite unlikely that it will run without modification on any
other database.
I'm not sure about MySQL, since I have no experience with it. But I've
read lots of comments indicating that MySQL is not very close to the
standards. I've never attempted to verify these comments, though. But if
they're true, then switching from MSDE to MySQL might prove to be very
hard.
Another issue is that some parts of SQL are not very standardised yet.
Procedural code, for instance, like triggers or stored procedures. Or
the declaration of supporting indexes - the options available are often
tied closely to the architecture of the database; some options available
for indexes on MSDE make sense only in the context of the mechanics of
how tables and indexes are stored in MSDE.
If you have no access to the source of the application and you can't
change the exact queries submitted, then I don't think you'll succeed.
SQL being a standardized and portable language does not imply that you
can just plug any database into an application and expect it to run.
What it does mean, is that *IF* the application is written with
portability in mind, it can be adapted to a new database with only
minimal changes.
Best, Hugo
(Remove _NO_ and _SPAM_ to get my e-mail address)
|||It takes quite a lot. MySQL has no stored procedures, and only the last
version has foreign keys. Then there is the following:
http://sql-info.de/mysql/gotchas.html
1.13 is a special favourite of mine...
Jacco Schalkwijk
SQL Server MVP
"claw" <claw@.hotmail.com> wrote in message
news:2005032101053516807%claw@.hotmailcom...
>I have a Windows XP application that uses MSDE as its DB engine. If I
>create an identical database in MySQL and include the correct ODBC
>"driver", is it be possible to replace MSDE with MySQL?
> What does it take for them to be compatible? After all both engines
> process SQL commands.
> Thanks for any input.
> - Alex