MSDE and Client Tools from SQLServer Eval

Ok, a while back, probably a year or so I started moving to MSDE. At the time a read posts on the Web that said you could use the client tools from the SQL Server Eval to manage MSDE. Great! I thought.

But more recently I get the impression that using those tools in not allowed. Can someone give me a diffinative answer.

I really want to stick with MSDE and am having a hard time convincing the boss to shell out $9,000+ for SQL Server on my dual processor web server. But I need DTS, Job Scheduling, etc...

Now my boss has wind of MySQL and knows that it's CHEAP.

If I can legally use the client tools with MSDE than I'm fine, if not I dread going to MySQL.

Your Advice is appreciated.Naturally you should check that your use of MSDEis appropriate.

If so do a Google on "Manage MSDE" and you'll get lots of hits. One popular one isthis one.

I think you can use DTS with MSDE but I don't know about scheduling as that is run by the Sql Server Agent which is a separate service. If you have a machine with just MSDE on it (i.e., not Sql Server) then look in the services to see if Sql Server Agent is running. If it's not there you'll have to create your own schedulerwhich isn't that hard.|||How about getting the Developer Edition of SQLServer and using the Client Tools to manage MSDE on the live server.|||If you read theappropriate uses that McMurdoStation posted, you will see what Microsoft has to say about that:

Q. Can I use SQL Server tools and services in conjunction with MSDE?

A. You can only use SQL Server tools and services in conjunction with MSDE if you acquired MSDE through SQL Server 2000 (Developer Edition, Standard Edition, or Enterprise Edition), and if you are using MSDE in conjunction with a properly licensed copy of SQL Server 2000. Visit the How to Buy page for information on obtaining a valid SQL Server license.

The following utilities are installed by the MSDE setup application and are provided without restrictions for use with the copy of MSDE that is installed by your application: bcp.exe, cnfgsvr.exe, dcomscm.exe, osql.exe, sqlmaint.exe, sqlmangr.exe, scm.exe, sqladhlp.exe, and svrnetcn.exe. The dtsrun.exe utility is also provided, but can only be used to run existing Data Transformation Services (DTS) packages against the copy of MSDE installed by your application; it cannot be used to develop new DTS packages.

Terri|||Yes, but it is not clear to me if the Developer Edition (Tools) can be used to manage a production MSDE engine.|||First a disclaimer: I am neither a lawyer or a Microsoft employee. I am only offering my opinion on the interpretation of what often looks to me like gobbledy-gook.

If you purchase SQL Server Developer edition, this comes with MSDE and the client tools. It says that you can use the tools and services with MSDE if you 1) acquired MSDE through SQL Server 2000 Developer edition and 2) you are using MSDE in conjunction with a properly licensed copy of SQL Server 2000.

So, you'd definitely have #1 covered.

However, for #2, theSQL Server 2000 Licensing FAQ says this: The SQL Server Developer edition is licensed per developer and must be used for designing, developing, and testing purposes only.

Putting all of that together, it seems that using the client tools that came with the Developer edition to manage a production database would be against the licensing terms.

Terri|||Maybe I think this because I want to, but it seems that if I buy Developer edition:

1) acquired MSDE through SQL Server 2000 Developer edition

Yep I bought it.

2) using MSDE in conjunction with a properly licensed copy of SQL Server 2000

Yep. I'm using MSDE with a Developer edition on my Dev server. The Dev server is only for designing, developing and testing. That doesn't mean that the MSDE needs to be development only. Does it?

I know I am splitting hairs.

I just called Microsoft and they said it was ok. Great!

I'm soooo glad I don't have to use MySQL

MSDE 2000 Question

Can you install the SQL client tools on a box running msde and register the msde database under enterprise manager?
Thanksyes, you cansql

MSDE 2000 installation problem

" Starting custom action ConfigServer
Executing "C:\Program Files\Microsoft SQL Server\80\Tools\Binn\cnfgsvr.exe
-V 1 -M 1 -U sa -I "MSSQLSERVER" -Q "Latin1_General""
Setup failed to configure the server. Refer to the server error logs and
setup error logs for more information. "
that is the last action before the install fail in the log
does anyone know what's wrong?
thanx
Lok
hi Lok,
"Lok" <Lok@.discussions.microsoft.com> ha scritto nel messaggio
news:7B1D91E0-00CA-4C32-AC67-267BCFF7958A@.microsoft.com
> " Starting custom action ConfigServer
> Executing "C:\Program Files\Microsoft SQL
> Server\80\Tools\Binn\cnfgsvr.exe -V 1 -M 1 -U sa -I "MSSQLSERVER" -Q
> "Latin1_General""
> Setup failed to configure the server. Refer to the server error logs
> and setup error logs for more information. "
> that is the last action before the install fail in the log
> does anyone know what's wrong?
> thanx
> Lok
please have a look at
http://support.microsoft.com/default...99&Product=sql
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 have tried every resolutions found on the website and it was still not
installing.
I've always set the lanaguage for non Unicode programs to chinese( Hong
Kong) to be able to display chinese character in the system natively. I have
specified the collation to Latin1_General in order for the setup to start but
the installation was never successful.
After switching the language back to English(United States), MSDE installed
fine.
Now my question is if I switch the language back to Chinese(Hong Kong),
would that mess up the MSDE install.
thanx
Lok
"Andrea Montanari" wrote:

> hi Lok,
> "Lok" <Lok@.discussions.microsoft.com> ha scritto nel messaggio
> news:7B1D91E0-00CA-4C32-AC67-267BCFF7958A@.microsoft.com
> please have a look at
> http://support.microsoft.com/default...99&Product=sql
> --
> 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
>

MSDE & SQL Server 2005 Mobile Server Tools problem

After installing MSDE(with SP4) and SQL Server 2000 SP4 Replication Components, the SQL Server 2005 Mobile Server Tools installation fails when running the System Configuration Check with a SQL Server requirement Error.

"You must first install the Replication Components for SQL Server 2000 SP 3a or higher or the SQL Server 2005 Replication Components"

Am I getting this error because I'm using the Desktop Engine version of the SQL Server 2000?

We have NOT tested SQL CE/Mobile Merge Replication with MSDE. And, we dont know the problems you may face.

Thanks,

Laxmi Narsimha Rao ORUGANTI, MSFT, SQL Mobile, Microsoft Corporation

|||

I've been using MSDE with SQL CE 2.0 without any problems.

With the release of Windows Mobile 5.0 I had to upgrade my applications using VS 2005 and start using SQL Server 2005 Mobile Edition instead of SQL CE2.0.

With SQL Server 2005 Express Edition things changed a little bit, because this version only works as a Subscriber when using Replication (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsse/html/sseoverview.asp).

The scenario is quite simple. After installing MSDE(SP4) in Windows XP Professional(SP2) and installing Microsoft SQL Server 2000 SP4 Replication Components and Microsoft .NET Framework 2.0 I try to install the SQL Server 2005 Mobile Server Tools, but during the System Configuration Check that error is displayed.

|||Any tips on how it can be achieved? MSDE - SqlCE merge replication I mean.
There is a problem which I'm trying to solve for quite some time:
SQL Server 2000 - SqlCE merge replication works just fine, but in MSDE -SqlCE scenario it seems to be some trouble.
I always get the same error: 29045 - reconciler has failed. Basically it means, that SqlCE server agent cannot start Reconciler under MSDE. What can cause such a disaster? Incompatibility of components used? This isnt connectivity or access rights issue, i'm pretty sure of it.
I've tried to use different versions of MSDE: MSDE SP4 and MSDE SP3a. Searching in different newsgroups for a couple of hours makes me think that older versions of MSDE are more suitable for my task because few posts stated that merge replication works on MSDE SP3a, but this subject isnt covered in detail. Can you provide any help?
|||

READ MY POST YESTERDAY

we are all waiting for Microsoft to bring this function

I will pay for it as you probably will as well

I dont understand why we are the only developers putting pressure on this matter

We need help. The other case is that we can begin referring other 3rd party non microsoft providers....

|||

You need to get onto my post and tell them you want it too

|||

If you are looking for SQL Mobile/SQL Ev to SQL Server synchronization you need to have either SQL Server 2000 or SQL Server 2005 Standard Edition and above.

Thanks

Laxmi Narsimha Rao ORUGNATI, MSFT, SQL Everywhere (SQL Ev), Microsoft Corp.

MSDE & SQL Server 2005 Mobile Server Tools problem

After installing MSDE(with SP4) and SQL Server 2000 SP4 Replication Components, the SQL Server 2005 Mobile Server Tools installation fails when running the System Configuration Check with a SQL Server requirement Error.

"You must first install the Replication Components for SQL Server 2000 SP 3a or higher or the SQL Server 2005 Replication Components"

Am I getting this error because I'm using the Desktop Engine version of the SQL Server 2000?

We have NOT tested SQL CE/Mobile Merge Replication with MSDE. And, we dont know the problems you may face.

Thanks,

Laxmi Narsimha Rao ORUGANTI, MSFT, SQL Mobile, Microsoft Corporation

|||

I've been using MSDE with SQL CE 2.0 without any problems.

With the release of Windows Mobile 5.0 I had to upgrade my applications using VS 2005 and start using SQL Server 2005 Mobile Edition instead of SQL CE2.0.

With SQL Server 2005 Express Edition things changed a little bit, because this version only works as a Subscriber when using Replication (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsse/html/sseoverview.asp).

The scenario is quite simple. After installing MSDE(SP4) in Windows XP Professional(SP2) and installing Microsoft SQL Server 2000 SP4 Replication Components and Microsoft .NET Framework 2.0 I try to install the SQL Server 2005 Mobile Server Tools, but during the System Configuration Check that error is displayed.

|||Any tips on how it can be achieved? MSDE - SqlCE merge replication I mean.
There is a problem which I'm trying to solve for quite some time:
SQL Server 2000 - SqlCE merge replication works just fine, but in MSDE -SqlCE scenario it seems to be some trouble.
I always get the same error: 29045 - reconciler has failed. Basically it means, that SqlCE server agent cannot start Reconciler under MSDE. What can cause such a disaster? Incompatibility of components used? This isnt connectivity or access rights issue, i'm pretty sure of it.
I've tried to use different versions of MSDE: MSDE SP4 and MSDE SP3a. Searching in different newsgroups for a couple of hours makes me think that older versions of MSDE are more suitable for my task because few posts stated that merge replication works on MSDE SP3a, but this subject isnt covered in detail. Can you provide any help?|||

READ MY POST YESTERDAY

we are all waiting for Microsoft to bring this function

I will pay for it as you probably will as well

I dont understand why we are the only developers putting pressure on this matter

We need help. The other case is that we can begin referring other 3rd party non microsoft providers....

|||

You need to get onto my post and tell them you want it too

|||

If you are looking for SQL Mobile/SQL Ev to SQL Server synchronization you need to have either SQL Server 2000 or SQL Server 2005 Standard Edition and above.

Thanks

Laxmi Narsimha Rao ORUGNATI, MSFT, SQL Everywhere (SQL Ev), Microsoft Corp.

MSDE & EM Tools

Hi,
I intend using MSDE 2000 in conjunction with a fully licensed version of SQL
Server 2000. MSDE will be installed on several clients.
My understanding is as follows :
I can use Enterprise Manager on any or all of those client instances of MSDE
because I have a fully licensed copy of SQL Server 2000 with which they will
be replicating.
MSDN:
You can only use SQL Server tools and services in conjunction with MSDE if
you acquired MSDE through SQL Server 2000 (Developer Edition, Standard
Edition, or Enterprise Edition), and if you are using MSDE in conjunction
with a properly licensed copy of SQL Server 2000.
Am I in the clear?
Can I use any of the GUI tools?
Thanks in advance,
DOM.hi Dom,
Dom wrote:
> Hi,
> I intend using MSDE 2000 in conjunction with a fully licensed version
> of SQL Server 2000. MSDE will be installed on several clients.
> My understanding is as follows :
> I can use Enterprise Manager on any or all of those client instances
> of MSDE because I have a fully licensed copy of SQL Server 2000 with
> which they will be replicating.
> MSDN:
> You can only use SQL Server tools and services in conjunction with
> MSDE if you acquired MSDE through SQL Server 2000 (Developer Edition,
> Standard Edition, or Enterprise Edition), and if you are using MSDE
> in conjunction with a properly licensed copy of SQL Server 2000.
> Am I in the clear?
> Can I use any of the GUI tools?
> Thanks in advance,
> DOM
please have a look at Steve Dybing answer in http://tinyurl.com/d2qpa .. it
does not seem this is a legal solution...
--
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply|||Thanks Andrea,
I followed the link you mentioned and on that page was directed to the
following site:
http://www.aspfaq.com/show.asp?id=2442
which states :
If you have an existing machine with SQL Server client tools installed, you
can manage the MSDE instance through these... as long as you have a valid an
d
legal Client Access License (CAL).
You can take the SQL Server install CD, run it on the client(s), and choose
"Install client tools only" during setup. This will install Query Analyzer,
Enterprise Manager, and other useful tools—but will not install the databa
se
engine.
This was my understanding.
With a fully licensed MSSQL 2000 you can legally use the client tools on
MSDE 2000 clients'
DOM|||hi Dom,
Dom wrote:
> Thanks Andrea,
> I followed the link you mentioned and on that page was directed to the
> following site:
> http://www.aspfaq.com/show.asp?id=2442
> which states :
> If you have an existing machine with SQL Server client tools
> installed, you can manage the MSDE instance through these... as long
> as you have a valid and legal Client Access License (CAL).
> You can take the SQL Server install CD, run it on the client(s), and
> choose "Install client tools only" during setup. This will install
> Query Analyzer, Enterprise Manager, and other useful tools-but will
> not install the database engine.
> This was my understanding.
> With a fully licensed MSSQL 2000 you can legally use the client tools
> on MSDE 2000 clients'
I had a private conversation with Steve some time ago about this matter...
he is not a "legal" guy too... but he has been told by legal representatives
that EM (QA and so on) is not legitimated to be used against production MSDE
instances... this is the reason he posted that way...
so, in my understanding, you never (or quite never, but I do really have no
idea when it could be legal) are legitimated to use SQL Server Client Tools
to manage MSDE...
my $0.02
--
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

MSDE & EM Tools

Hi,
I intend using MSDE 2000 in conjunction with a fully licensed version of SQL
Server 2000. MSDE will be installed on several clients.
My understanding is as follows :
I can use Enterprise Manager on any or all of those client instances of MSDE
because I have a fully licensed copy of SQL Server 2000 with which they will
be replicating.
MSDN:
You can only use SQL Server tools and services in conjunction with MSDE if
you acquired MSDE through SQL Server 2000 (Developer Edition, Standard
Edition, or Enterprise Edition), and if you are using MSDE in conjunction
with a properly licensed copy of SQL Server 2000.
Am I in the clear?
Can I use any of the GUI tools?
Thanks in advance,
DOM.
hi Dom,
Dom wrote:
> Hi,
> I intend using MSDE 2000 in conjunction with a fully licensed version
> of SQL Server 2000. MSDE will be installed on several clients.
> My understanding is as follows :
> I can use Enterprise Manager on any or all of those client instances
> of MSDE because I have a fully licensed copy of SQL Server 2000 with
> which they will be replicating.
> MSDN:
> You can only use SQL Server tools and services in conjunction with
> MSDE if you acquired MSDE through SQL Server 2000 (Developer Edition,
> Standard Edition, or Enterprise Edition), and if you are using MSDE
> in conjunction with a properly licensed copy of SQL Server 2000.
> Am I in the clear?
> Can I use any of the GUI tools?
> Thanks in advance,
> DOM
please have a look at Steve Dybing answer in http://tinyurl.com/d2qpa .. it
does not seem this is a legal solution...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Thanks Andrea,
I followed the link you mentioned and on that page was directed to the
following site:
http://www.aspfaq.com/show.asp?id=2442
which states :
If you have an existing machine with SQL Server client tools installed, you
can manage the MSDE instance through these... as long as you have a valid and
legal Client Access License (CAL).
You can take the SQL Server install CD, run it on the client(s), and choose
"Install client tools only" during setup. This will install Query Analyzer,
Enterprise Manager, and other useful tools—but will not install the database
engine.
This was my understanding.
With a fully licensed MSSQL 2000 you can legally use the client tools on
MSDE 2000 clients?
DOM
|||hi Dom,
Dom wrote:
> Thanks Andrea,
> I followed the link you mentioned and on that page was directed to the
> following site:
> http://www.aspfaq.com/show.asp?id=2442
> which states :
> If you have an existing machine with SQL Server client tools
> installed, you can manage the MSDE instance through these... as long
> as you have a valid and legal Client Access License (CAL).
> You can take the SQL Server install CD, run it on the client(s), and
> choose "Install client tools only" during setup. This will install
> Query Analyzer, Enterprise Manager, and other useful tools-but will
> not install the database engine.
> This was my understanding.
> With a fully licensed MSSQL 2000 you can legally use the client tools
> on MSDE 2000 clients?
I had a private conversation with Steve some time ago about this matter...
he is not a "legal" guy too... but he has been told by legal representatives
that EM (QA and so on) is not legitimated to be used against production MSDE
instances... this is the reason he posted that way...
so, in my understanding, you never (or quite never, but I do really have no
idea when it could be legal) are legitimated to use SQL Server Client Tools
to manage MSDE...
my $0.02
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

MSDE & EM Tools

Hi,
I intend using MSDE 2000 in conjunction with a fully licensed version of SQL
Server 2000. MSDE will be installed on several clients.
My understanding is as follows :
I can use Enterprise Manager on any or all of those client instances of MSDE
because I have a fully licensed copy of SQL Server 2000 with which they will
be replicating.
MSDN:
You can only use SQL Server tools and services in conjunction with MSDE if
you acquired MSDE through SQL Server 2000 (Developer Edition, Standard
Edition, or Enterprise Edition), and if you are using MSDE in conjunction
with a properly licensed copy of SQL Server 2000.
Am I in the clear?
Can I use any of the GUI tools?
Thanks in advance,
DOM.hi Dom,
Dom wrote:
> Hi,
> I intend using MSDE 2000 in conjunction with a fully licensed version
> of SQL Server 2000. MSDE will be installed on several clients.
> My understanding is as follows :
> I can use Enterprise Manager on any or all of those client instances
> of MSDE because I have a fully licensed copy of SQL Server 2000 with
> which they will be replicating.
> MSDN:
> You can only use SQL Server tools and services in conjunction with
> MSDE if you acquired MSDE through SQL Server 2000 (Developer Edition,
> Standard Edition, or Enterprise Edition), and if you are using MSDE
> in conjunction with a properly licensed copy of SQL Server 2000.
> Am I in the clear?
> Can I use any of the GUI tools?
> Thanks in advance,
> DOM
please have a look at Steve Dybing answer in http://tinyurl.com/d2qpa .. it
does not seem this is a legal solution...
--
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply|||Thanks Andrea,
I followed the link you mentioned and on that page was directed to the
following site:
http://www.aspfaq.com/show.asp?id=2442
which states :
If you have an existing machine with SQL Server client tools installed, you
can manage the MSDE instance through these... as long as you have a valid and
legal Client Access License (CAL).
You can take the SQL Server install CD, run it on the client(s), and choose
"Install client tools only" during setup. This will install Query Analyzer,
Enterprise Manager, and other useful toolsâ'but will not install the database
engine.
This was my understanding.
With a fully licensed MSSQL 2000 you can legally use the client tools on
MSDE 2000 clients'
DOM|||hi Dom,
Dom wrote:
> Thanks Andrea,
> I followed the link you mentioned and on that page was directed to the
> following site:
> http://www.aspfaq.com/show.asp?id=2442
> which states :
> If you have an existing machine with SQL Server client tools
> installed, you can manage the MSDE instance through these... as long
> as you have a valid and legal Client Access License (CAL).
> You can take the SQL Server install CD, run it on the client(s), and
> choose "Install client tools only" during setup. This will install
> Query Analyzer, Enterprise Manager, and other useful tools-but will
> not install the database engine.
> This was my understanding.
> With a fully licensed MSSQL 2000 you can legally use the client tools
> on MSDE 2000 clients'
I had a private conversation with Steve some time ago about this matter...
he is not a "legal" guy too... but he has been told by legal representatives
that EM (QA and so on) is not legitimated to be used against production MSDE
instances... this is the reason he posted that way...
so, in my understanding, you never (or quite never, but I do really have no
idea when it could be legal) are legitimated to use SQL Server Client Tools
to manage MSDE...
my $0.02
--
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

Msde

When setting up the MSDE should you be able to connect to it ... from another machine using Sql client tools via enterprise manager...like you would connecting to machines that have sql standard editionyou have to have a port open in your windows firewall if you are doing this one a workstation. MSDE also shuts down after the last connection closes and you have to change that.|||MSDE can also be set up to not listen on any network protocol. Check the errorlog of MSDE to make sure it is listening on the network.|||By default network connections to MSDE are disabled. However, you can change that in the instance settings.

Also, as far as I know, all versions of SQL Server 2005 don't allow network connections by default as well. But yet again, that can all be changed in the configuration manager.|||we are mainly connection to sql 2000 machines...
I can connect to instantly from visual studio .net 2003 through the server explorer... but through client tools via enterprise manager its a no go...
I set up the instance with the parameter setting DISABLENETWORKPROTOCOLS=0 so that the instance can accept connections....