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 along side WMSDE?

I've got a situation where WSUS is already installed on a server and I'm
looking
at moving my anti-virus system on to the same server, however my AV uses
MSDE. The server is running 2003 and therefore WSUS is running in WMSDE.
I take it I can't use WMSDE for my AV solution so I'd like to know, is it
viable to simply install MSDE 2000 along side WMSDE, or will I have to move
WSUS out of WMSDE and into MSDE 2000?
I assume I'll have some conflicts at minimum with the ports clashing if the
two live together, and there are likely to be other major problems.
Does anyone have any ideas or suggestions?
hi,
AC wrote:
> I've got a situation where WSUS is already installed on a server and
> I'm looking
> at moving my anti-virus system on to the same server, however my AV
> uses MSDE. The server is running 2003 and therefore WSUS is running
> in WMSDE.
> I take it I can't use WMSDE for my AV solution so I'd like to know,
> is it viable to simply install MSDE 2000 along side WMSDE, or will I
> have to move WSUS out of WMSDE and into MSDE 2000?
> I assume I'll have some conflicts at minimum with the ports clashing
> if the two live together, and there are likely to be other major
> problems.
> Does anyone have any ideas or suggestions?
WMSDE should not be used for other means then the ones it has been released
for, so just install another instance of MSDE for your AV...
you'll have no "ports clashing" or conflicts, as SQL Server 2000 allows up
to 16 instances to be locally installed...
only one of them can be the "default" instance, litening (by default) on
TCP/IP 1433 where all other instances have to be named instances, where
their full name is composed by the ComputerName\InstanceName...
you can leave for all of them the default "dynamically assigned port"
setting, an additional service, the SQL Server Resolution Service is then
listening on UDP 1434 to resolve and address the correct named instance on
it's appropriate port..
if you manually set the TCP/IP port the named instance(s) will be listen on,
you can close (on your firewall) the UDP 1434 port as it is no longer
needed, but you'll probably need to specify an ALIAS (via Client Network
Utility, cliconfg.exe) on all your remote clients..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Thank you very much for your reply Andrea.
Although I've seen installations with several MSDE instances before I never
thought about how they worked untill now, therefore I've never even realised
there is a manager service to resolve the ports for each service!
Thank you for enlightening to this!
"Andrea Montanari" wrote:

> hi,
> AC wrote:
> WMSDE should not be used for other means then the ones it has been released
> for, so just install another instance of MSDE for your AV...
> you'll have no "ports clashing" or conflicts, as SQL Server 2000 allows up
> to 16 instances to be locally installed...
> only one of them can be the "default" instance, litening (by default) on
> TCP/IP 1433 where all other instances have to be named instances, where
> their full name is composed by the ComputerName\InstanceName...
> you can leave for all of them the default "dynamically assigned port"
> setting, an additional service, the SQL Server Resolution Service is then
> listening on UDP 1434 to resolve and address the correct named instance on
> it's appropriate port..
> if you manually set the TCP/IP port the named instance(s) will be listen on,
> you can close (on your firewall) the UDP 1434 port as it is no longer
> needed, but you'll probably need to specify an ALIAS (via Client Network
> Utility, cliconfg.exe) on all your remote clients..
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
>
sql

MSDE & database moving.

Hi,

How to copy database diagram (all data) to other server using only MSDE
server and VS.Net Proffesional? I have no Enterprice manager. I have to
move database (create on my machine) to my customer server. Is some
possibilities?
--
*Pozdrawiam,*
Klaudiusz Bryjahi,
"bryja_klaudiusz[at]poczta[dot]fm" <dla@.zmyly.pl> ha scritto nel messaggio
news:c67ou4$i2p$1@.atlantis.news.tpi.pl...
> Hi,
> How to copy database diagram (all data) to other server using only MSDE
> server and VS.Net Proffesional? I have no Enterprice manager. I have to
> move database (create on my machine) to my customer server. Is some
> possibilities?
> --
> *Pozdrawiam,*
> Klaudiusz Bryja
you actually have 3 possibilities..
1)
you can detach your database(s), copy all the physical files you database is
made of to you user's server and re-attach the database using the system
stored procedure
EXEC sp_detach_db 'database_name' -- for detaching
and
EXEC sp_attach_db @.dbname = 'dbname'
, @.filename1 = 'c:\...\physical_position_Datafile.Mdf'
, @.filenameN = 'c:\...\physical_position_Logfile.Ldf'

ah... you have to re-attach the database to your server to, after copying
the files to a distribution media...
up to 16 data and log files can be specified, but please have a look at
http://msdn.microsoft.com/library/d..._ae-az_52oy.asp
for sp_attch_db synopsis and syntax...

2)
you can (full) backup you database(s) and restore it to your user's server
using
RESTORE DATABASE database_name
FROM DISK = 'c:\...\backup.bck'
WITH MOVE 'logical_Datafile_name' TO 'c:\..\newDataFilePosition.Mdf'
MOVE 'logical_Logfile_name' TO 'c:\..\newLogFilePosition.Ldf'

the WITH MOVE option grants you the possibility to specify alternate
physical positions on user's server, other than your original locations on
your dev server
please have a look at
http://msdn.microsoft.com/library/d..._ra-rz_25rm.asp
for Transact SQL backup syntax.

both these 2 methods are easy to implement, they can be performed on user's
server using ADO/AdoNet commands as long as via oSql.exe or similar tools...
they suffer a common scenario... you will restoring your database, based on
your model database, with your server settings regarding collation/sort
order, database options (autogrowth, autoshrink, size, recovery model and so
on), and more, they miss the ability to inherits objects/users existing in
user's model database.. another issue is you can propagate "orphaned users"
troubles if you not correctly purge your distribution database before
distributing it (more about "orphaned users" at
http://www.sqlservercentral.com/col...rokenlogins.asp)

3)
another way is to script out your database structure using tools like
Enterprise Manager or ObjectScripter, provided for free by MVP OJ at
http://www.rac4sql.net/objectscriptr_main.asp...
once the structure is exported to file, you can easily script out table
contents creating INSERT INTO sql scripts to be run in order to reload
pre-poluated tables, using the well known procedure provided by MVP Narayana
Vyas Kondreddi at http://vyaskn.tripod.com/code.htm#inserts (there are
other variations of that available on the net)
personally I do prefer this method, which grant me greater and more granular
control, where I can provide T-SQL DDL scripts, INSERT INTO scripts as long
as BCP possibility for larger tables/views.. this comes in handy for
structure version sync to, becouse the tool you provide for database
distribution can be prepared for upgrading database structure too.. and all
user's server and database settings are respected...
this method grants greater flexibility at the cost of greater complexity...
hth
--
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtm http://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|||Hi,

Thanks. It helped.

>hi,
>"bryja_klaudiusz[at]poczta[dot]fm" <dla@.zmyly.pl> ha scritto nel messaggio
>news:c67ou4$i2p$1@.atlantis.news.tpi.pl...
>
>>Hi,
>>
>>How to copy database diagram (all data) to other server using only MSDE
>>server and VS.Net Proffesional? I have no Enterprice manager. I have to
>>move database (create on my machine) to my customer server. Is some
>>possibilities?
>>--
>>*Pozdrawiam,*
>>Klaudiusz Bryja
>>
>>
>>
>you actually have 3 possibilities..
>1)
>you can detach your database(s), copy all the physical files you database is
>made of to you user's server and re-attach the database using the system
>stored procedure
>EXEC sp_detach_db 'database_name' -- for detaching
>and
>EXEC sp_attach_db @.dbname = 'dbname'
> , @.filename1 = 'c:\...\physical_position_Datafile.Mdf'
> , @.filenameN = 'c:\...\physical_position_Logfile.Ldf'
>ah... you have to re-attach the database to your server to, after copying
>the files to a distribution media...
>up to 16 data and log files can be specified, but please have a look at
>http://msdn.microsoft.com/library/d..._ae-az_52oy.asp
>for sp_attch_db synopsis and syntax...
>2)
>you can (full) backup you database(s) and restore it to your user's server
>using
>RESTORE DATABASE database_name
> FROM DISK = 'c:\...\backup.bck'
> WITH MOVE 'logical_Datafile_name' TO 'c:\..\newDataFilePosition.Mdf'
> MOVE 'logical_Logfile_name' TO 'c:\..\newLogFilePosition.Ldf'
>the WITH MOVE option grants you the possibility to specify alternate
>physical positions on user's server, other than your original locations on
>your dev server
>please have a look at
>http://msdn.microsoft.com/library/d..._ra-rz_25rm.asp
>for Transact SQL backup syntax.
>both these 2 methods are easy to implement, they can be performed on user's
>server using ADO/AdoNet commands as long as via oSql.exe or similar tools...
>they suffer a common scenario... you will restoring your database, based on
>your model database, with your server settings regarding collation/sort
>order, database options (autogrowth, autoshrink, size, recovery model and so
>on), and more, they miss the ability to inherits objects/users existing in
>user's model database.. another issue is you can propagate "orphaned users"
>troubles if you not correctly purge your distribution database before
>distributing it (more about "orphaned users" at
>http://www.sqlservercentral.com/col...rokenlogins.asp)
>3)
>another way is to script out your database structure using tools like
>Enterprise Manager or ObjectScripter, provided for free by MVP OJ at
>http://www.rac4sql.net/objectscriptr_main.asp...
>once the structure is exported to file, you can easily script out table
>contents creating INSERT INTO sql scripts to be run in order to reload
>pre-poluated tables, using the well known procedure provided by MVP Narayana
>Vyas Kondreddi at http://vyaskn.tripod.com/code.htm#inserts (there are
>other variations of that available on the net)
>personally I do prefer this method, which grant me greater and more granular
>control, where I can provide T-SQL DDL scripts, INSERT INTO scripts as long
>as BCP possibility for larger tables/views.. this comes in handy for
>structure version sync to, becouse the tool you provide for database
>distribution can be prepared for upgrading database structure too.. and all
>user's server and database settings are respected...
>this method grants greater flexibility at the cost of greater complexity...
>hth

MSDE - moving a copy of a database and reloading onto another PC

I need to the best way to make a copy(Backup/export) of the data base put in on a CD or e-mail it. Have instructions to import or restore the database onto another PC.
Also in the C:\Program Files\Microsoft SQL Server\80\Tools\Binn>
What and how does dtsrun.exe work?
Thanks
These articles might help ..
314546 HOW TO: Move Databases Between Computers That Are Running SQL Server
http://support.microsoft.com/?id=314546
240872 HOW TO: Resolve Permission Issues When You Move a Database Between
http://support.microsoft.com/?id=240872
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.
|||These articles might help ..
314546 HOW TO: Move Databases Between Computers That Are Running SQL Server
http://support.microsoft.com/?id=314546
240872 HOW TO: Resolve Permission Issues When You Move a Database Between
http://support.microsoft.com/?id=240872
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.

MSDE - moving a copy of a database and reloading onto another PC

I need to the best way to make a copy(Backup/export) of the data base put in on a CD or e-mail it. Have instructions to import or restore the database onto another PC.
Also in the C:\Program Files\Microsoft SQL Server\80\Tools\Binn>
What and how does dtsrun.exe work?
Thanks
Please refer to these articles that might help -
314546 HOW TO: Move Databases Between Computers That Are Running SQL Server
http://support.microsoft.com/?id=314546
240872 HOW TO: Resolve Permission Issues When You Move a Database Between
http://support.microsoft.com/?id=240872
Cheers,
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.
|||Please refer to these articles that might help -
314546 HOW TO: Move Databases Between Computers That Are Running SQL Server
http://support.microsoft.com/?id=314546
240872 HOW TO: Resolve Permission Issues When You Move a Database Between
http://support.microsoft.com/?id=240872
Cheers,
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.