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 and backup-restore

I'm using Msde on a PC with XP SP2 acting as "server" and accessing a
database on a PC with XP SP2 acting as "client". I can backup my database
from the "client" using UNC format
"\\client.computer.name\share.name\file.name.b kp" but when trying to restore
it from the "client" PC i get errors. Any ideas about how to restore the bkp
file to server pc from the client without having to copy the bkp file to the
server and perform the restore from there? Thanks
hi,
Dithom wrote:
> I'm using Msde on a PC with XP SP2 acting as "server" and accessing a
> database on a PC with XP SP2 acting as "client". I can backup my
> database from the "client" using UNC format
> "\\client.computer.name\share.name\file.name.b kp" but when trying to
> restore it from the "client" PC i get errors. Any ideas about how to
> restore the bkp file to server pc from the client without having to
> copy the bkp file to the server and perform the restore from there?
> Thanks
what kind of exception do you get?
actually if you can backup on a remote share you should be able to restore
from it too..
the account(s) running the SQL Server and SQL Server Agent must have enought
privileges on the remote share...
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

MSDE 2GB Limit

Hi
A Client has an MSDE install - checked by running @.@.version (clearly
says developer edition in the result text).
However the size of the data file is over 3GB, even allowing for empty
spaces the amount of data far exceeds 2GB. Pls explain?
The database was filled by regular insert statements.
Am 31 Oct 2005 04:14:49 -0800 schrieb yitzak:

> Hi
> A Client has an MSDE install - checked by running @.@.version (clearly
> says developer edition in the result text).
> However the size of the data file is over 3GB, even allowing for empty
> spaces the amount of data far exceeds 2GB. Pls explain?
> The database was filled by regular insert statements.
MSDE always shows "Desktop Engine" and not "Developer Edition"!
bye,
Helmut

MSDE 2000A Upgrade to SQL Express SP1 with Merge Replication

Hello,

I have the following scenario. An application using SQL Server 2000 SP3 on the server side and clients using MSDE 2000A (SP3a) on the client machine. Since the client is offline quite often merge replication is used to keep the clients in sync.

Now we try to upgrade to SQL Server 2005 SP1. The publisher and distributor upgrade (on the same box) worked fine and all clients could still synchronize. Fine :-)

Now we try to upgrade the clients to SQL Express SP1. Now the problems start :-(

1) After the upgrade the entry within the Synchronization Manager is gone (we can overcome this by using sp_MSregistersubscription or by manually disable and enable Synchronization manager on the subscription properties)

2) Initial Synchronization (takes a long time but) works fine, if I apply changes to the subscriber or force a reinitialize all following synchronization will fail. With the following messages:

Error messages:
The merge process could not clean up the subscription to 'tstvmw23':'TestBase:'TestBase'. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147200965)
Get help: http://help/MSSQL_REPL-2147200965
New request is not allowed to start because it should come with valid transaction descriptor. (Source: MSSQLServer, Error number: 3989)
Get help: http://help/3989

Remark the test system I use is a nearly empty db (only with full schema and a few lookup tables) with 15MB. The same error occures if I create a new database an subscribe to the same publication.

Please help otherwise I'm forced to step back to MSDE.

Thanks in advance,

Thomas Hotz

Hi,

just to make sure you do not want SQL Server Express to the a merge replicant...

http://msdn2.microsoft.com/en-us/library/ms165616.aspx

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de|||What this table on the BOL means is that SQL Server Express cannot act as a Distributor/Publisher on a merge replication and the main cause is that it does not have an Agent.
http://technet.microsoft.com/en-us/library/ms143470.aspx
See the topic SQL Server does not include an agent on that reference.

SQL Server Express can act as a subscriber on Merge Replication though. If you have a type of subscription Pull, as the Agent runs on the subscribers you have to use RMO on your code to instantiate an agent or use Windows Synchronization Manager (Start Menu-> Accessories -> Synchronize)

We have SQLE running as subscribers on a pull merge replication topology...sql

MSDE 2000A Upgrade to SQL Express SP1 with Merge Replication

Hello,

I have the following scenario. An application using SQL Server 2000 SP3 on the server side and clients using MSDE 2000A (SP3a) on the client machine. Since the client is offline quite often merge replication is used to keep the clients in sync.

Now we try to upgrade to SQL Server 2005 SP1. The publisher and distributor upgrade (on the same box) worked fine and all clients could still synchronize. Fine :-)

Now we try to upgrade the clients to SQL Express SP1. Now the problems start :-(

1) After the upgrade the entry within the Synchronization Manager is gone (we can overcome this by using sp_MSregistersubscription or by manually disable and enable Synchronization manager on the subscription properties)

2) Initial Synchronization (takes a long time but) works fine, if I apply changes to the subscriber or force a reinitialize all following synchronization will fail. With the following messages:

Error messages:
The merge process could not clean up the subscription to 'tstvmw23':'TestBase:'TestBase'. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147200965)
Get help: http://help/MSSQL_REPL-2147200965
New request is not allowed to start because it should come with valid transaction descriptor. (Source: MSSQLServer, Error number: 3989)
Get help: http://help/3989

Remark the test system I use is a nearly empty db (only with full schema and a few lookup tables) with 15MB. The same error occures if I create a new database an subscribe to the same publication.

Please help otherwise I'm forced to step back to MSDE.

Thanks in advance,

Thomas Hotz

Hi,

just to make sure you do not want SQL Server Express to the a merge replicant...

http://msdn2.microsoft.com/en-us/library/ms165616.aspx

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de
|||What this table on the BOL means is that SQL Server Express cannot act as a Distributor/Publisher on a merge replication and the main cause is that it does not have an Agent.
http://technet.microsoft.com/en-us/library/ms143470.aspx
See the topic SQL Server does not include an agent on that reference.

SQL Server Express can act as a subscriber on Merge Replication though. If you have a type of subscription Pull, as the Agent runs on the subscribers you have to use RMO on your code to instantiate an agent or use Windows Synchronization Manager (Start Menu-> Accessories -> Synchronize)

We have SQLE running as subscribers on a pull merge replication topology...

MSDE 2000 Set-up: Invalid instance name

Thanks in advance.

I installed SQL 2000 Client Portion in my local computer: No server functionality. I selected my computer name as an instance name. Installation went OK.

Now, I am trying to install MSDE in my computer. Error comes in early part of installation: It says, "The instance name specified is not valid"

Please, any advise and suggestion.

Try deinstalling the SQL Client (why did that ask for an instance name when you didn't install the server - are you sure about deselecting the server?)

Install MSDE after the SQL Client was deinstalled. MSDE 2000 comes with a readme which explains the command line options for the setup. Read it carefully.

--
SvenC

|||

Thanks.

By the way, I have SQL 2005 Server in my computer.

Maybe, this is why.

|||

Yes, presumably MSDE tries to use the same instance name already in use by SQL 2005. Why would you want both versions on one machine?

Well, you can do it, but check the MSDE readme how to configure a different instance name. In the connection string you will use servername\instancename to access the named instance.

--
SvenC

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 and Windows 2003

I am having trouble connecting to a Windows 2003 w/ MSDE 2000 from all my client PCs. I can connect locally from my Server. I have no firewalls or any other devices in between my clients and server.
Did you enable network connection on msde? Use svrnetcn.exe.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Jiffy" <anonymous@.discussions.microsoft.com> wrote in message
news:94F601EF-E2C2-4777-BDB8-DDC76DFFE97A@.microsoft.com...
> I am having trouble connecting to a Windows 2003 w/ MSDE 2000 from all my client PCs. I can connect locally
from my Server. I have no firewalls or any other devices in between my clients and server.
|||After you do this you will need to stop and restart MSDE.
Rand
This posting is provided "as is" with no warranties and confers no rights.

MSDE 2000 and Windows 2003

I am having trouble connecting to a Windows 2003 w/ MSDE 2000 from all my cl
ient PCs. I can connect locally from my Server. I have no firewalls or any o
ther devices in between my clients and server.Did you enable network connection on msde? Use svrnetcn.exe.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Jiffy" <anonymous@.discussions.microsoft.com> wrote in message
news:94F601EF-E2C2-4777-BDB8-DDC76DFFE97A@.microsoft.com...
> I am having trouble connecting to a Windows 2003 w/ MSDE 2000 from all my client P
Cs. I can connect locally
from my Server. I have no firewalls or any other devices in between my clien
ts and server.|||After you do this you will need to stop and restart MSDE.
Rand
This posting is provided "as is" with no warranties and confers no rights.

MSDE 2000 & SQL Server 7 installed together?

Hi group!
I'm developing an application using Access/SQL Server.
The end client (government...) only has SQL server 7
installed and has not plans to upgrade in the development
timeframe.
I'd like to use SQL Server 2000 functions in my app. So
I'm wondering if I can reccomend an installation of MSDE
2000 alongside their SLQ server 7.
Is this technically possible?
If not, I'll have to rethink my design and do it in SQL
Server 7.
TIA
Andrew
hi Andrew,
"Andrew Webster" <andrew@.SPAM_ME_NOTwebster.org> ha scritto nel messaggio
news:042701c499fd$d7915ca0$a601280a@.phx.gbl...
> Hi group!
> I'm developing an application using Access/SQL Server.
> The end client (government...) only has SQL server 7
> installed and has not plans to upgrade in the development
> timeframe.
> I'd like to use SQL Server 2000 functions in my app. So
> I'm wondering if I can reccomend an installation of MSDE
> 2000 alongside their SLQ server 7.
> Is this technically possible?
> If not, I'll have to rethink my design and do it in SQL
> Server 7.
MSDE 2000 and MSDE 1.0, as long as SQL Server 7.0 and SQL Server 2000, and
relative mix, can coexiste on the same server...
the 7.0 code based server will be the default instance while the 2000 code
based server(s) have to be named instances.. up to 16 different isntances of
SQL Server 2000/MSDE 2000 can be (technically) hosted on the same sarver...
MDAC stack will be updated at 2.6 version (minimum requirement for SQL
Server 2000 RTM version), or better at 2.7.1 for service pack 3a level,
which I strongly recommend.
if you install MSDE 2000 over SQL Server 7.0, all the client tools of the
7.0 edition should be unusable as the COM binaries will be replaced with the
higher version, and only 2000 based tools will be available for management..
one caveat.. MSDE does not provide those tools (Enterprise Manager, Query
Analyzer and so on) but only the COM objects they rely on... so I really
have no idea (never tried myself) what the end position will be...
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
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
|||Thanks for that - I've now got access to a machine with SQL 7.0 on it, so I
can have a go at the installation and see how it works.
Andrew
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:2qojtiF127domU1@.uni-berlin.de...
> hi Andrew,
> "Andrew Webster" <andrew@.SPAM_ME_NOTwebster.org> ha scritto nel messaggio
> news:042701c499fd$d7915ca0$a601280a@.phx.gbl...
> MSDE 2000 and MSDE 1.0, as long as SQL Server 7.0 and SQL Server 2000, and
> relative mix, can coexiste on the same server...
> the 7.0 code based server will be the default instance while the 2000 code
> based server(s) have to be named instances.. up to 16 different isntances
of
> SQL Server 2000/MSDE 2000 can be (technically) hosted on the same
sarver...
> MDAC stack will be updated at 2.6 version (minimum requirement for SQL
> Server 2000 RTM version), or better at 2.7.1 for service pack 3a level,
> which I strongly recommend.
> if you install MSDE 2000 over SQL Server 7.0, all the client tools of the
> 7.0 edition should be unusable as the COM binaries will be replaced with
the
> higher version, and only 2000 based tools will be available for
management..
> one caveat.. MSDE does not provide those tools (Enterprise Manager, Query
> Analyzer and so on) but only the COM objects they rely on... so I really
> have no idea (never tried myself) what the end position will be...
> --
> 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
> --
> 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 / ODBC install problem...please help...

I have installed MSDE (and ODBC) at my client site on their 2003 server. I
have attached my SQL database via Teratrax Database Manager to the MSDE
server however when I try to setup the ODBC connection it doesn't list the
database in the drop-down. I cannot attach to the database from my notebook
either because I am not authenticated onto their domain.
I have also applied the regedit on the LoginMode key setting it to 2 and
rebooted but I still cannot connect to the database via the ODBC manager.
What am I doing wrong? I am NOT good with the scripts for configuring things
- generally I use the Enterprise Manager.
Try running the client config (cliconfig.exe) and create an alias for the
server. Specify the protocol to talk to it - (probably TCP/IP vs. named
pipes). On my system its in \windows\system32.
Brian
"Chris" <Chris@.discussions.microsoft.com> wrote in message
news:46518420-EF43-475F-BECA-9E5A7E6A21D2@.microsoft.com...
>I have installed MSDE (and ODBC) at my client site on their 2003 server. I
> have attached my SQL database via Teratrax Database Manager to the MSDE
> server however when I try to setup the ODBC connection it doesn't list the
> database in the drop-down. I cannot attach to the database from my
> notebook
> either because I am not authenticated onto their domain.
> I have also applied the regedit on the LoginMode key setting it to 2 and
> rebooted but I still cannot connect to the database via the ODBC manager.
> What am I doing wrong? I am NOT good with the scripts for configuring
> things
> - generally I use the Enterprise Manager.

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 ,SSMSE connection

hi friends,

I'll be thankful if anyone solve this problem.

When i developed my application, i used sql 2000 as a server side DB.
Now my client want to install MSDE instead of SQL 2000.

so i uninstall SQL2000 and installed MSDE .

AS we all know, MSDE doesn't have GUI. So i installed Microsoft SQL Server Management Studio Express - Community Technology Preview (CTP)
(includeing xmlparser,windows installer,.net 2.0).

now i could able to view tables and everything. but i couldn't make the connection. Getting error like "SQL server not found. CMPNAME\MSDERELA"
I used same kind of connection string for SQL 2000. Worked well.here what happened?

Connection String : "Data Source = CMPNAME\MSDERELA;Database =TEST; User id ="xxx; Password =xxxx;"

OS: Windows server 2003.
i used VB.NET to develop the apps. (VS2003). Connecting from Pocket PC.

kindly help me to solve this problem.

(Already i posted this in SQL tools forum. i hope this is the right place to post this question. so posting again.)

Thank u!

First I suggest you install the release version of SSMS-E.

Then can you go into the services panel in Windows and see if there are any services that start with MSSQL$, if there are please make sure it is started.

If it is started then please test the connection by using osql from a cmd prompt.

|||

You mean i need to install SSMSE before installing MSDE?

Let me share, what i 've done

1) installed MSDE

2)Windows installer 3.1

3).net framework 2

4)XML Parser

5) SSMSE

6) Start the MSDE agent and enabled TCP/IP.

Only thing is, i didn't check the connection in command prompt.

I checked with apps.

Thanks.

|||

So you know for sure the the MSSQL$ service is running (not the agent service)?

Can you please try connecting using osql from the command line please?

MSDE & SSMSE -CTP connection problem

hi friends,

I'll be thankful if anyone solve this problem.

When i developed my application i used sql 2000 as a server side DB.
Now my client want to install MSDE instead of SQL 2000.

so i uninstall SQL2000 and installed MSDE .

AS we all know, MSDE doesn't have GUI. So i installed Microsoft SQL Server Management Studio Express - Community Technology Preview (CTP)
(includeing xmlparser,windows installer,.net 2.0).

now i could able to view tables and everything. but i couldn't make the connection. Getting error like "SQL server not found. CMPNAME\MSDERELA"
I used same kind of connection string for SQL 2000. Worked well.here what happened?

OS: Windows server 2003.
i used VB.NET to develop the apps.

kindly help me to solve this problem.

why do you need to have a gui interface on the same box. you can connect to it from another SQL client machine/Server.|||

I don't understand ur point.

My server machine has MSDE DB only.

Clients are Pocket PCs.

|||? Hi, I have seen one other person with a problem like this when they created a SQL Server database from Visual Studio. Can you confirm that MSDE is installed as a named instance MSDERELA? Open a command shell window and type the following: SQLCMD -S .\MSDERELA What do you see? If you see a prompt like this: 1> then you are able to connect to the instance using SQLCMD which is a start. I notice that you have a CTP installed. You need to be VERY careful when you later come to uninstall this and go to SSMSE RTM build. There is a specific order in which to uninstall items to achieve a successful uninstall. Andrew Watt MVP <ar_pad@.discussions.microsoft.com> wrote in message news:434cb1f0-4b2c-43c5-97da-5aea1f39295f@.discussions.microsoft.com... hi friends, I'll be thankful if anyone solve this problem. When i developed my application i used sql 2000 as a server side DB.Now my client want to install MSDE instead of SQL 2000. so i uninstall SQL2000 and installed MSDE . AS we all know, MSDE doesn't have GUI. So i installed Microsoft SQL Server Management Studio Express - Community Technology Preview (CTP) (includeing xmlparser,windows installer,.net 2.0). now i could able to view tables and everything. but i couldn't make the connection. Getting error like "SQL server not found. CMPNAME\MSDERELA"I used same kind of connection string for SQL 2000. Worked well.here what happened? OS: Windows server 2003.i used VB.NET to develop the apps. kindly help me to solve this problem.|||

Hi,

Yes. It's a named instance. computername\MSDERelA.

can i use the same cmd? SQLCMD -S .\MSDERELA where can i see these kind of commands?

I followed this order. 1) windows installer

2)dotnetfx.exe

3)msxml6.msi

4) SSMSE

is it correct?

Thanks!

|||

That's the right order to install Management Studio Express.

The command line syntax for sqlcmd is very similar to the syntax for osql. You can get the command line syntax for sqlcmd by typing the following in a command window:

sqlcmd /?

"sqlcmd -S .\msderela -E" will connect to your local msderela instance using Windows authentication. You can type "quit" to exit sqlcmd.

Here's the online help topic for sqlcmd: http://msdn2.microsoft.com/en-us/library/ms165702(SQL.90).aspx

Hope this helps,
Steve

MSDE & SSMSE -CTP connection problem

hi friends,

I'll be thankful if anyone solve this problem.

When i developed my application i used sql 2000 as a server side DB.
Now my client want to install MSDE instead of SQL 2000.

so i uninstall SQL2000 and installed MSDE .

AS we all know, MSDE doesn't have GUI. So i installed Microsoft SQL Server Management Studio Express - Community Technology Preview (CTP)
(includeing xmlparser,windows installer,.net 2.0).

now i could able to view tables and everything. but i couldn't make the connection. Getting error like "SQL server not found. CMPNAME\MSDERELA"
I used same kind of connection string for SQL 2000. Worked well.here what happened?

OS: Windows server 2003.
i used VB.NET to develop the apps.

kindly help me to solve this problem.

why do you need to have a gui interface on the same box. you can connect to it from another SQL client machine/Server.|||

I don't understand ur point.

My server machine has MSDE DB only.

Clients are Pocket PCs.

|||? Hi, I have seen one other person with a problem like this when they created a SQL Server database from Visual Studio. Can you confirm that MSDE is installed as a named instance MSDERELA? Open a command shell window and type the following: SQLCMD -S .\MSDERELA What do you see? If you see a prompt like this: 1> then you are able to connect to the instance using SQLCMD which is a start. I notice that you have a CTP installed. You need to be VERY careful when you later come to uninstall this and go to SSMSE RTM build. There is a specific order in which to uninstall items to achieve a successful uninstall. Andrew Watt MVP <ar_pad@.discussions.microsoft.com> wrote in message news:434cb1f0-4b2c-43c5-97da-5aea1f39295f@.discussions.microsoft.com... hi friends, I'll be thankful if anyone solve this problem. When i developed my application i used sql 2000 as a server side DB.Now my client want to install MSDE instead of SQL 2000. so i uninstall SQL2000 and installed MSDE . AS we all know, MSDE doesn't have GUI. So i installed Microsoft SQL Server Management Studio Express - Community Technology Preview (CTP) (includeing xmlparser,windows installer,.net 2.0). now i could able to view tables and everything. but i couldn't make the connection. Getting error like "SQL server not found. CMPNAME\MSDERELA"I used same kind of connection string for SQL 2000. Worked well.here what happened? OS: Windows server 2003.i used VB.NET to develop the apps. kindly help me to solve this problem.|||

Hi,

Yes. It's a named instance. computername\MSDERelA.

can i use the same cmd? SQLCMD -S .\MSDERELA where can i see these kind of commands?

I followed this order. 1) windows installer

2)dotnetfx.exe

3)msxml6.msi

4) SSMSE

is it correct?

Thanks!

|||

That's the right order to install Management Studio Express.

The command line syntax for sqlcmd is very similar to the syntax for osql. You can get the command line syntax for sqlcmd by typing the following in a command window:

sqlcmd /?

"sqlcmd -S .\msderela -E" will connect to your local msderela instance using Windows authentication. You can type "quit" to exit sqlcmd.

Here's the online help topic for sqlcmd: http://msdn2.microsoft.com/en-us/library/ms165702(SQL.90).aspx

Hope this helps,
Steve

MSDE & SQL 2000

I have a client that has a server running Windows 2000 Server. another
company has installed MSDE (version unknown) on this server. I need to
install SQL 2000 on the same server. Will the two coexist peacefully?

Tia
CruznOz

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!Certainly; I have had both on a test machine for a couple of months. But
you will have to tell your application code which one to connect to.

N. Shamsundar
University of Houston

CruznOz wrote:
> I have a client that has a server running Windows 2000 Server. another
> company has installed MSDE (version unknown) on this server. I need to
> install SQL 2000 on the same server. Will the two coexist peacefully?
> Tia
> CruznOz
>
> *** Sent via Developersdex http://www.developersdex.com ***
> Don't just participate in USENET...get rewarded for it!

msde

Can MSDE be used on computer in different cities? Say the server in Dallas
and the client computer in Houston. Or is the full SQL Server required?In article <a1vWc.504738$Gx4.25752@.bgtnsc04-news.ops.worldnet.att.net>,
kpsklab@.worldnet.att.net says...
> Can MSDE be used on computer in different cities? Say the server in Dallas
> and the client computer in Houston. Or is the full SQL Server required?

MSDE is the desktop database, where it runs in not a question, it can
run were you install it based on the license restrictions. The real
question should be "How do I securely access a MSDE database running in
another city?"

As long as you properly follow the license restrictions you can install
MSDE anywhere.

As for connecting, use a VPN tunnel - do not directly expose the MSDE
(or any other service) to the internet unless you know security inside
and out. A VPN from one location to the other is painless to setup and
means that all of your data/connection is secure and not directly
exposed to the internet.

--
--
spamfree999@.rrohio.com
(Remove 999 to reply to me)

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....

msdb restore

I have a client who is trying to restore an old backup of
the msdb database. Of course, their new build of SQL is
different, so they can't do the restore. We get an error
similar to:
"Server: Msg 3168, Level 16, State 1, Line 1
The backup of the system database on device
d:\temp\master.bak cannot be restored because it was
created by a different version of the server (134217904)
than this server (134217920).
Server: Msg 3013, Level 16, State 1, Line 1
RESTORE DATABASE is terminating abnormally. "
what I need to know is how to interpret the version number
in the error message - i.e. "134217904" so I can figure
out what version they need to have running in order to
restore. Anyone have any ideas?
Thanks!Take a look at Q264474. That will help you :-)
/Peter
"Lia" <lkeston@.patriotsoftware.biz> wrote in message
news:4cdc01c3d5fb$f1edd8b0$7d02280a@.phx.gbl...
> I have a client who is trying to restore an old backup of
> the msdb database. Of course, their new build of SQL is
> different, so they can't do the restore. We get an error
> similar to:
> "Server: Msg 3168, Level 16, State 1, Line 1
> The backup of the system database on device
> d:\temp\master.bak cannot be restored because it was
> created by a different version of the server (134217904)
> than this server (134217920).
> Server: Msg 3013, Level 16, State 1, Line 1
> RESTORE DATABASE is terminating abnormally. "
> what I need to know is how to interpret the version number
> in the error message - i.e. "134217904" so I can figure
> out what version they need to have running in order to
> restore. Anyone have any ideas?
> Thanks!
>|||The following command should tell you what build of SQL Server the backup
was taken from:
RESTORE HEADERONLY
FROM DISK = 'd:\temp\master.bak '
You can look at http://support.microsoft.com/?id=264474 for further
information.
Rand
This posting is provided "as is" with no warranties and confers no rights.

msdb renamed to msbd

Hello,
Yesterday i was trying to install a backup client for sql on our sql server,
it kept on failing so i contacted the software vendor to see if there was a
problem with the client. after they poked around on our sql server they rea
lized that one of the datab
ases had been renamed, for what reason i dont know. The msdb database was re
named to msbd. This is the reason that we can not install the backup agent s
oftware. Does anyone out there know how to rename the database, the physical
name of the database file
is fine its the display name inside of Enterprise manager.
ThanksHi,
Refer sp_renamedb in books online
sp_renamedb [ @.dbname = ] 'old_name' ,
[ @.newname = ] 'new_name'
Thanks
Hari
MCDBA
"Brian Butler" <anonymous@.discussions.microsoft.com> wrote in message
news:564BE6BC-5201-4828-A0B3-9E1450653B3A@.microsoft.com...
> Hello,
> Yesterday i was trying to install a backup client for sql on our sql
server, it kept on failing so i contacted the software vendor to see if
there was a problem with the client. after they poked around on our sql
server they realized that one of the databases had been renamed, for what
reason i dont know. The msdb database was renamed to msbd. This is the
reason that we can not install the backup agent software. Does anyone out
there know how to rename the database, the physical name of the database
file is fine its the display name inside of Enterprise manager.
> Thanks|||In SQL 2000, an alternative to sp_renamedb is ALTER DATABASE:
ALTER DATABASE msbd
MODIFY NAME = msdb
Hope this helps.
Dan Guzman
SQL Server MVP
"Brian Butler" <anonymous@.discussions.microsoft.com> wrote in message
news:564BE6BC-5201-4828-A0B3-9E1450653B3A@.microsoft.com...
> Hello,
> Yesterday i was trying to install a backup client for sql on our sql
server, it kept on failing so i contacted the software vendor to see if
there was a problem with the client. after they poked around on our sql
server they realized that one of the databases had been renamed, for what
reason i dont know. The msdb database was renamed to msbd. This is the
reason that we can not install the backup agent software. Does anyone out
there know how to rename the database, the physical name of the database
file is fine its the display name inside of Enterprise manager.
> Thanks