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 / EM licensing

I'm aware you can install MSDE on a customers site if they dont have SQL
Server, correct? If so can you install the client setup off the SQL Server
cd so you get enterprise manager?
How do you handle backup/restore 'nicely' without EM?
LH
If so can you install the client setup off the SQL Server
> cd so you get enterprise manager?
-No, that would break the EULA.

> How do you handle backup/restore 'nicely' without EM?
-There aremany free tools outside to use:
One example: https://www.whitebearconsulting.com/Utilities.htm
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
"lh" <lh@.nowhere.com> schrieb im Newsbeitrag
news:_q1xe.22580$Le2.144904@.nasal.pacific.net.au.. .
> I'm aware you can install MSDE on a customers site if they dont have SQL
> Server, correct? If so can you install the client setup off the SQL
> Server cd so you get enterprise manager?
> How do you handle backup/restore 'nicely' without EM?
>
> LH
>

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

msdb.dbo.sysjobschedules less columns

msdb.dbo.sysjobschedules shows columns
scheduke_id,job_id,next_rundate,next_run
_time in MS Sqlserver 2005 beta3.
but the document (help) tells "name","enabled","freq_type","freq_interval"
too.
These columns were present in MS sqlserver 2000.
1. Is it that, some configuration is missing in my sql server 2005 beta3 DB?
2. or Do I need to do join with some other view/table to get these details.
Best regards,
Amit Kumar.Dear Amit,
I've got the CTP June for Sql Server 2005 and it happens the same.
""This topic is pre-release documentation and is subject to change in future
releases. Blank topics are included as placeholders.]""
Best regards,
"Amit Kumar" wrote:

> msdb.dbo.sysjobschedules shows columns
> scheduke_id,job_id,next_rundate,next_run
_time in MS Sqlserver 2005 beta3.
> but the document (help) tells "name","enabled","freq_type","freq_interval"
> too.
> These columns were present in MS sqlserver 2000.
> 1. Is it that, some configuration is missing in my sql server 2005 beta3 D
B?
> 2. or Do I need to do join with some other view/table to get these details
.
> Best regards,
> Amit Kumar.
>

MSDB suspect

Hi,
What are the steps I should execute if MSDB database is showing suspect.
The conditions is we dont have a backup but the sqlserver is running.Look at the sql server logs and see what might have caused this. Look in bol for sp_resetstatus. Worst case scenario, you will have to detach the msdb and run instmsdb.sql to recreate (however, you will lose all information stored in the msdb - DTS packages, scheduled tasks, backup/restore history, replication).

Oh yes - One last step - BACKUP ... :-)

MSDB Corrupt?

[298] SQLServer Error: 446, Cannot resolve collation conflict for equal
to operation. [SQLSTATE 42000]
I keep getting this from SQL Agent. I restored an msdb database from an
old SQL Server and i am now finding out that it had a different
collation on it. how do i fix the msdb?in sql2000 you can change the collation of a column and
database. Read "changing collations" in sql BOL.
>--Original Message--
>[298] SQLServer Error: 446, Cannot resolve collation
conflict for equal
>to operation. [SQLSTATE 42000]
>I keep getting this from SQL Agent. I restored an msdb
database from an
>old SQL Server and i am now finding out that it had a
different
>collation on it. how do i fix the msdb?
>.
>|||Is there anyway to completely rebuild msdb (get a fresh one?)
anonymous@.discussions.microsoft.com wrote:
> in sql2000 you can change the collation of a column and
> database. Read "changing collations" in sql BOL.
>
>>--Original Message--
>>[298] SQLServer Error: 446, Cannot resolve collation
> conflict for equal
>>to operation. [SQLSTATE 42000]
>>I keep getting this from SQL Agent. I restored an msdb
> database from an
>>old SQL Server and i am now finding out that it had a
> different
>>collation on it. how do i fix the msdb?
>>.|||I know there was a rebuildmsdb utility in SQL &. You could drop msdb
and create msdb again, then run a utility to create all the tables and
procedures. is there one for sql 2000?
anonymous@.discussions.microsoft.com wrote:
> in sql2000 you can change the collation of a column and
> database. Read "changing collations" in sql BOL.
>
>>--Original Message--
>>[298] SQLServer Error: 446, Cannot resolve collation
> conflict for equal
>>to operation. [SQLSTATE 42000]
>>I keep getting this from SQL Agent. I restored an msdb
> database from an
>>old SQL Server and i am now finding out that it had a
> different
>>collation on it. how do i fix the msdb?
>>.|||the following article should also apply to sql2000.
http://support.microsoft.com/default.aspx?scid=kb;en-
us;238822
>--Original Message--
>I know there was a rebuildmsdb utility in SQL &. You
could drop msdb
>and create msdb again, then run a utility to create all
the tables and
>procedures. is there one for sql 2000?
>
>anonymous@.discussions.microsoft.com wrote:
>> in sql2000 you can change the collation of a column and
>> database. Read "changing collations" in sql BOL.
>>
>>--Original Message--
>>[298] SQLServer Error: 446, Cannot resolve collation
>> conflict for equal
>>to operation. [SQLSTATE 42000]
>>I keep getting this from SQL Agent. I restored an msdb
>> database from an
>>old SQL Server and i am now finding out that it had a
>> different
>>collation on it. how do i fix the msdb?
>>.
>.
>|||> the following article should also apply to sql2000.
That is only the repository, not the whole msdb.
instmsdb.sql will build msdb. But search KB and the net on instruction on how to use it first.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
<anonymous@.discussions.microsoft.com> wrote in message
news:037f01c39e5c$ff4a5ff0$a301280a@.phx.gbl...
> the following article should also apply to sql2000.
> http://support.microsoft.com/default.aspx?scid=kb;en-
> us;238822
> >--Original Message--
> >I know there was a rebuildmsdb utility in SQL &. You
> could drop msdb
> >and create msdb again, then run a utility to create all
> the tables and
> >procedures. is there one for sql 2000?
> >
> >
> >anonymous@.discussions.microsoft.com wrote:
> >
> >> in sql2000 you can change the collation of a column and
> >> database. Read "changing collations" in sql BOL.
> >>
> >>
> >>
> >>--Original Message--
> >>[298] SQLServer Error: 446, Cannot resolve collation
> >>
> >> conflict for equal
> >>
> >>to operation. [SQLSTATE 42000]
> >>
> >>I keep getting this from SQL Agent. I restored an msdb
> >>
> >> database from an
> >>
> >>old SQL Server and i am now finding out that it had a
> >>
> >> different
> >>
> >>collation on it. how do i fix the msdb?
> >>
> >>.
> >>
> >
> >.
> >

MSDb and Master maintenance

Using the Database Maintenenace Plan Wizard I set up
maintenance plans for each of the databases on my MS SQL
Server. This is working fine except for the "msdb"
and "master" databases. For these I get the following
errors. What am I doing wrong?
Microsoft (R) SQLMaint Utility (Unicode), Version Logged
on to SQL Server 'EPDDOCS3' as 'NT AUTHORITY\SYSTEM'
(trusted)
Starting maintenance plan 'DB Maintenance Plan msdb' on
9/20/2004 8:00:01 AM
[1] Database msdb: Check Data and Index Linkage...
** Execution Time: 0 hrs, 0 mins, 1 secs **
Backup can not be performed on database 'msdb'. This sub
task is ignored.
End of maintenance plan 'DB Maintenance Plan msdb' on
9/20/2004 8:00:02 AM
SQLMAINT.EXE Process Exit Code: 1 (Failed)
Microsoft (R) SQLMaint Utility (Unicode), Version Logged
on to SQL Server 'EPDDOCS3' as 'NT AUTHORITY\SYSTEM'
(trusted)
Starting maintenance plan 'DB Maintenance Plan msdb' on
9/20/2004 4:00:01 AM
[1] Database msdb: Check Data and Index Linkage...
** Execution Time: 0 hrs, 0 mins, 1 secs **
Backup can not be performed on database 'msdb'. This sub
task is ignored.
End of maintenance plan 'DB Maintenance Plan msdb' on
9/20/2004 4:00:02 AM
SQLMAINT.EXE Process Exit Code: 1 (Failed)
You probably try to do log backups. You can't do log backup on master. You can on model, but that is
overkill and would require setting it to full recovery mode. I suggest you create two plans, One in
which you do log backup, another in which you don't.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"John Schuster" <schuster@.llnl.gov> wrote in message news:4aa201c49f30$4fc629d0$a601280a@.phx.gbl...
> Using the Database Maintenenace Plan Wizard I set up
> maintenance plans for each of the databases on my MS SQL
> Server. This is working fine except for the "msdb"
> and "master" databases. For these I get the following
> errors. What am I doing wrong?
> Microsoft (R) SQLMaint Utility (Unicode), Version Logged
> on to SQL Server 'EPDDOCS3' as 'NT AUTHORITY\SYSTEM'
> (trusted)
> Starting maintenance plan 'DB Maintenance Plan msdb' on
> 9/20/2004 8:00:01 AM
> [1] Database msdb: Check Data and Index Linkage...
> ** Execution Time: 0 hrs, 0 mins, 1 secs **
> Backup can not be performed on database 'msdb'. This sub
> task is ignored.
> End of maintenance plan 'DB Maintenance Plan msdb' on
> 9/20/2004 8:00:02 AM
> SQLMAINT.EXE Process Exit Code: 1 (Failed)
> ----
> Microsoft (R) SQLMaint Utility (Unicode), Version Logged
> on to SQL Server 'EPDDOCS3' as 'NT AUTHORITY\SYSTEM'
> (trusted)
> Starting maintenance plan 'DB Maintenance Plan msdb' on
> 9/20/2004 4:00:01 AM
> [1] Database msdb: Check Data and Index Linkage...
> ** Execution Time: 0 hrs, 0 mins, 1 secs **
> Backup can not be performed on database 'msdb'. This sub
> task is ignored.
> End of maintenance plan 'DB Maintenance Plan msdb' on
> 9/20/2004 4:00:02 AM
> SQLMAINT.EXE Process Exit Code: 1 (Failed)
>