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 Access via the Network

I'm having a terrible time accessing an MSDE instance over the network.
sqlDMO's listAvailableSQLServers doesn't see the installed instance. I
installed the MSDE instance using setup.exe with the following command:
setup.exe disablenetworkprotocols=0 sapwd="<pwd>" securityMode=SQL
instanceName="<my instance name>"
No luck. So I thought I'd use the svrnetcn.exe utility to enable network
protocols since MSDE seems to be ignoring the command line. When I try to run
svrnetcn.exe, the screen flickers but the program never opens.
This *was* working several weeks ago. It quit working about the time I
installed Service Pack 2 for Windows XP on the box that was hosting this
server. Does anyone have any idea why this is happening to me? Any help
would be GREATLY appreciated.
Rob Reagan
rob@.digitallabsinc.com
hi Rob,
"Rob Reagan" <RobReagan@.discussions.microsoft.com> ha scritto nel messaggio
news:5B63E3CB-8307-49C8-ABC4-56B114893B1D@.microsoft.com...
> I'm having a terrible time accessing an MSDE instance over the network.
> sqlDMO's listAvailableSQLServers doesn't see the installed instance. I
> installed the MSDE instance using setup.exe with the following command:
> setup.exe disablenetworkprotocols=0 sapwd="<pwd>" securityMode=SQL
> instanceName="<my instance name>"
> No luck. So I thought I'd use the svrnetcn.exe utility to enable network
> protocols since MSDE seems to be ignoring the command line. When I try to
run
> svrnetcn.exe, the screen flickers but the program never opens.
> This *was* working several weeks ago. It quit working about the time I
> installed Service Pack 2 for Windows XP on the box that was hosting this
> server. Does anyone have any idea why this is happening to me? Any help
> would be GREATLY appreciated.
> Rob Reagan
> rob@.digitallabsinc.com
>
SP service pack 2 changed a lot of things regarding SQL Server connections
too..
I've not installed sp2 yet, but it's worth reading
http://support.microsoft.com/default.aspx?kbid=841249 and related links...
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
|||Thank you so much! That's just the information I needed.
SP2 makes my PC so secure, not even my own applications can get through...
"Andrea Montanari" wrote:

> hi Rob,
> "Rob Reagan" <RobReagan@.discussions.microsoft.com> ha scritto nel messaggio
> news:5B63E3CB-8307-49C8-ABC4-56B114893B1D@.microsoft.com...
> run
> SP service pack 2 changed a lot of things regarding SQL Server connections
> too..
> I've not installed sp2 yet, but it's worth reading
> http://support.microsoft.com/default.aspx?kbid=841249 and related links...
> --
> 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 2000 with Access 2003: The First steps

Finally got to the point where I can connect to MSDE from Access. If you are setting up MSDE for the first time, you may find a couple useful points in the following.
MSDE 2000 with Access 2003: The First steps.
1) install MSDE from Office CD (need to locate in MSDE directory by browsing and start it manually. Read KB article 319930 first);
2) when installing, need to specify "sa" (system admin) password which is not (does not have to be anyway) the same as Windows Administrator's password. It is required in order not to leave sysadmin password blank which would leave a security hole;
3) if you are using all the correct switches with the 'setup' command, the mixed login mode will be allowed. The mixed login mode lets you login from non-admin account by using MSDE login. I did not use any switches so had to make the adjustments in the r
egistry. Very easy, but I still had to locate the required key which was not where it is supposed to be judging from KB article 319930, but quite near it.
4) restart and check that 2 new services are running: MSSQLSERVER and SQLSERVERAGENT.
5) restart the PC and log in under (Windows) administrator account (does not need to be THE "Administrator", just any account with admin privileges)
6) test the connection to MDSE by going to command line, typing "osql -E" (no " needed). You should see ">1" which means MDSE is running.
7) Now this is the $100 trick: type "sp_addlogin [BUILTIN\POWER USERS]", <ENTER>, "GO". wait for some reaction (something like 2 rows affected)
8) Here comes another $100 trick: type "grant all", <ENTER>, "to [BUILTIN\POWER USERS]", <ENTER>, "go".
Now you can go back to your every day Windows login (I assume you are using an account from Power Users group, aren't you?), start Access, create a new .adp file and connect your Access .adp file to MSDE using "Trusted Connection" or "Use Windows NT integ
rated security".
Oh by the way you can type "exit" from command line to stop your connection to MSDE when you feel like.
You can also submit commands and scripts via OSQL directly from the command
line. I thought from your previous post that you were trying to 'assign
(SQL) sysadmin permissions to a newly created (SQL) account.' I.e., your
SQL account was already created and you were trying to put it in the
sysadmin server role. By the way,
$50 Discount - GRANT grants database-specific permissions to users. So if
you have more than one Database, you need to use GRANT on all databases and
database objects you want the user to have access to.
$0.02 worth - sp_addrolemember and sp_addsrvrolemember adds users to
server-wide roles, like "sysadmin." GRANT is database object specific, so
it works only on individual databases and database objects (tables, etc.)
Cheers,
Michael C.
"Lolik" <Lolik@.discussions.microsoft.com> wrote in message
news:BDFB3614-78ED-4DB2-8468-7C78073A7906@.microsoft.com...
> Finally got to the point where I can connect to MSDE from Access. If you
are setting up MSDE for the first time, you may find a couple useful points
in the following.
> MSDE 2000 with Access 2003: The First steps.
> 1) install MSDE from Office CD (need to locate in MSDE directory by
browsing and start it manually. Read KB article 319930 first);
> 2) when installing, need to specify "sa" (system admin) password which is
not (does not have to be anyway) the same as Windows Administrator's
password. It is required in order not to leave sysadmin password blank which
would leave a security hole;
> 3) if you are using all the correct switches with the 'setup' command, the
mixed login mode will be allowed. The mixed login mode lets you login from
non-admin account by using MSDE login. I did not use any switches so had to
make the adjustments in the registry. Very easy, but I still had to locate
the required key which was not where it is supposed to be judging from KB
article 319930, but quite near it.
> 4) restart and check that 2 new services are running: MSSQLSERVER and
SQLSERVERAGENT.
> 5) restart the PC and log in under (Windows) administrator account (does
not need to be THE "Administrator", just any account with admin privileges)
> 6) test the connection to MDSE by going to command line, typing "osql -E"
(no " needed). You should see ">1" which means MDSE is running.
> 7) Now this is the $100 trick: type "sp_addlogin [BUILTIN\POWER USERS]",
<ENTER>, "GO". wait for some reaction (something like 2 rows affected)
> 8) Here comes another $100 trick: type "grant all", <ENTER>, "to
[BUILTIN\POWER USERS]", <ENTER>, "go".
> Now you can go back to your every day Windows login (I assume you are
using an account from Power Users group, aren't you?), start Access, create
a new .adp file and connect your Access .adp file to MSDE using "Trusted
Connection" or "Use Windows NT integrated security".
> Oh by the way you can type "exit" from command line to stop your
connection to MSDE when you feel like.
|||$0.02 worth - sp_addrolemember and sp_addsrvrolemember adds users to
server-wide roles, like "sysadmin." GRANT is database object specific, so
it works only on individual databases and database objects (tables, etc.)
__________________
Do not underestimate your input Michael!
Guess I should run sp_addsrvrolemember too. Still after having used GRANT as above I was able to create a new SQL database and connect to it, at the time a new Access .adp file was set up.
The $50 tag referred to using [BUILTIN\POWER USERS] as a login. Could not find it mentioned anywhere. Maybe it is obvious to everyone but me but figuring out what [Corporate\Bobj] is in XP language was not straightforward to me at all.
|||Yes, you can grant User Groups access rights to your SQL Server One of
the benefits of using Integrated Security for your SQL Server logins. The
built-in server roles, like sysadmin grant general permissions server-wide,
and include various other little niceties. Since your user created the 2nd
database, that user is the database owner (dbo) for that database, so that
user will have all the rights associated with that database. Server Roles
make it a little easier to admin multiple databases.
Cheers,
Michael C.

> Do not underestimate your input Michael!
> Guess I should run sp_addsrvrolemember too. Still after having used GRANT
as above I was able to create a new SQL database and connect to it, at the
time a new Access .adp file was set up.
sql

MSDE 2000 Timeout when restoring a database

Hello,

I have been trying to restore a database to the msde but I keep getting a timeout when it happens. Does anyone know how to increase the time before a timeout is called?

I have restored a different, and smaller, database to the MSDE 2000 and it is Ok so I know everything else is OK.

Regards,

Ian.

Hello,

I should mention that i need to be able to change the Timeout from the command line and not using the supplied application. This is to be installed on the users PC and it needs to be automatic.

Regards,

Ian.

|||

How is the RESTORE statement being requested?

Control over the timeout is handled by the requesting application.

As far as I know, there is no way to set a default timeout for all applications.

As far as I know, the default timeout is infinite. So perhaps your application is explicitly requesting a timeout from the client access interface it uses.

Hope that helps.

sql

MSDE 2000 Replication Conflict

I am using MSDE 2000 for my replication. the problem is that althought at time creating publication it inserts GUID into every table but if one table in 2 nodes has same primary key, it inserts only one row ( accorrding to prority ). there are some Conflict Reslover methods that can be used for this purpose. i wanted to ask that is there any other way for me to resolve this conflict. i am asking for a new way because my database schema has been created and a lot of coding behalf of that schema has been done.

I'd be thankful if you guide me.
Regards,

Are you trying to insert the same primary key at both nodes? In your case, conflict resolver won't work for you because although you have inserted at both nodes, they are treated as different rows with different rowguid. What are you trying to achieve in this scenario? Do rows with same primary key stand for the same thing in your business scenario?

You can also refer to this post to see if you have the same problem: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=509453&SiteID=1

Hope it helps

Wanwen

|||Dear Wanwen.

i have a scenario as follows.

I have one publisher and two subscribers. a table called "Companies" is my article. That "Companies" table has a primary key column called CompanyId which is an Identity Row. Now when i insert data into subscribers i will have two rows with same Primary key. For Example two rows with CompanyId 1. Now at time of merging data, i want both companyIds ( both rows with Pk 1 ) be present in publisher. But at reality it does not happen.

What should i do?! because i need both rows at publisher .

Note: i have to mention that at time of creating Subscription GUID is included by SQL Server. So why is it not working?!

Regards,|||

In your case, you need to use identity range management. Please refer to BOL topic: Replicating Identity Columns. Basically, to use identity columns in a replication topology that has updates at more than one node, each node in the replication topology must use a different range of identity values, so that duplicates do not occur. You could use auto for Identity Range Management Option and specify @.pub_identity_range, @.identity_range and @.threshold.

Rowguid column added by replication is for change tracking, conflict detecting and resolving, not for failure to apply changes due to constraint.

Hope it helps.

Wanwen

sql

MSDE 2000 help please

Hi,
I downloaded MSDE 2000 but it's my first time using it and I dont know what
i'm doing. I'm using coldfusion for database driven websites. I can make
databases by using osql in a command prompt but is there an easier way? also
where does the server save the databases that i create? I cant find anything
on my system after i created a basic db.
Any help would be appreciated,
Thanks> I can make
> databases by using osql in a command prompt but is there an easier way?
http://www.aspfaq.com/2442

> also where does the server save the databases that i create?
The data and objects are stored in MDF files on your hard drive. They don't
really have any meaning independently (e.g. you can't open them in notepad
or Excel and look at them like you would in Access or other desktop
applications).

> I cant find anything
> on my system after i created a basic db.
Well, what did you do to "create a basic db"? What are you looking for on
your system?
A|||> Well, what did you do to "create a basic db"? What are you looking for on
> your system?
to start i did osql -E in a command prompt, then I did CREATE DATABASE
Study. Now I cant find the database in my hard drive. I'm "looking" for it s
o
i can use it in coldfusion server. I need to point to a physical file to
register that db so I can manipulate it in my web pages.The documentation on
how to do such things arent very available on the ms knowledge base. At leas
t
IMO
Phil|||It does not work this way. You can't point an application at a data file
for SQL Server and expect to "manipulate it in your web pages."
However, go ahead, look for the file, it will be called study_data.mdf, most
likely.
Let us know when you run out of ideas trying to point ColdFusion at that
file and banging your head against the wall.
You might consider checking ColdFusion documentation; there's plenty of
information available about SQL Server and MSDE in the knowledge base
(perhaps you just aren't sure what to look for).
http://www.aspfaq.com/
(Reverse address to reply.)
"Skinman" <Skinman@.discussions.microsoft.com> wrote in message
news:730E0313-4155-47E0-A309-B43AB5A10660@.microsoft.com...
on[vbcol=seagreen]
> to start i did osql -E in a command prompt, then I did CREATE DATABASE
> Study. Now I cant find the database in my hard drive. I'm "looking" for it
so
> i can use it in coldfusion server. I need to point to a physical file to
> register that db so I can manipulate it in my web pages.The documentation
on
> how to do such things arent very available on the ms knowledge base. At
least
> IMO
> Phil

MSDE 2000 help please

Hi,
I downloaded MSDE 2000 but it's my first time using it and I dont know what
i'm doing. I'm using coldfusion for database driven websites. I can make
databases by using osql in a command prompt but is there an easier way? also
where does the server save the databases that i create? I cant find anything
on my system after i created a basic db.
Any help would be appreciated,
Thanks
> I can make
> databases by using osql in a command prompt but is there an easier way?
http://www.aspfaq.com/2442

> also where does the server save the databases that i create?
The data and objects are stored in MDF files on your hard drive. They don't
really have any meaning independently (e.g. you can't open them in notepad
or Excel and look at them like you would in Access or other desktop
applications).

> I cant find anything
> on my system after i created a basic db.
Well, what did you do to "create a basic db"? What are you looking for on
your system?
A
|||> Well, what did you do to "create a basic db"? What are you looking for on
> your system?
to start i did osql -E in a command prompt, then I did CREATE DATABASE
Study. Now I cant find the database in my hard drive. I'm "looking" for it so
i can use it in coldfusion server. I need to point to a physical file to
register that db so I can manipulate it in my web pages.The documentation on
how to do such things arent very available on the ms knowledge base. At least
IMO
Phil
|||It does not work this way. You can't point an application at a data file
for SQL Server and expect to "manipulate it in your web pages."
However, go ahead, look for the file, it will be called study_data.mdf, most
likely.
Let us know when you run out of ideas trying to point ColdFusion at that
file and banging your head against the wall.
You might consider checking ColdFusion documentation; there's plenty of
information available about SQL Server and MSDE in the knowledge base
(perhaps you just aren't sure what to look for).
http://www.aspfaq.com/
(Reverse address to reply.)
"Skinman" <Skinman@.discussions.microsoft.com> wrote in message
news:730E0313-4155-47E0-A309-B43AB5A10660@.microsoft.com...[vbcol=seagreen]
on
> to start i did osql -E in a command prompt, then I did CREATE DATABASE
> Study. Now I cant find the database in my hard drive. I'm "looking" for it
so
> i can use it in coldfusion server. I need to point to a physical file to
> register that db so I can manipulate it in my web pages.The documentation
on
> how to do such things arent very available on the ms knowledge base. At
least
> IMO
> Phil

MSDE 2000 help please

Hi,
I downloaded MSDE 2000 but it's my first time using it and I dont know what
i'm doing. I'm using coldfusion for database driven websites. I can make
databases by using osql in a command prompt but is there an easier way? also
where does the server save the databases that i create? I cant find anything
on my system after i created a basic db.
Any help would be appreciated,
Thanks> I can make
> databases by using osql in a command prompt but is there an easier way?
http://www.aspfaq.com/2442
> also where does the server save the databases that i create?
The data and objects are stored in MDF files on your hard drive. They don't
really have any meaning independently (e.g. you can't open them in notepad
or Excel and look at them like you would in Access or other desktop
applications).
> I cant find anything
> on my system after i created a basic db.
Well, what did you do to "create a basic db"? What are you looking for on
your system?
A|||> Well, what did you do to "create a basic db"? What are you looking for on
> your system?
to start i did osql -E in a command prompt, then I did CREATE DATABASE
Study. Now I cant find the database in my hard drive. I'm "looking" for it so
i can use it in coldfusion server. I need to point to a physical file to
register that db so I can manipulate it in my web pages.The documentation on
how to do such things arent very available on the ms knowledge base. At least
IMO
Phil|||It does not work this way. You can't point an application at a data file
for SQL Server and expect to "manipulate it in your web pages."
However, go ahead, look for the file, it will be called study_data.mdf, most
likely.
Let us know when you run out of ideas trying to point ColdFusion at that
file and banging your head against the wall.
You might consider checking ColdFusion documentation; there's plenty of
information available about SQL Server and MSDE in the knowledge base
(perhaps you just aren't sure what to look for).
--
http://www.aspfaq.com/
(Reverse address to reply.)
"Skinman" <Skinman@.discussions.microsoft.com> wrote in message
news:730E0313-4155-47E0-A309-B43AB5A10660@.microsoft.com...
> > Well, what did you do to "create a basic db"? What are you looking for
on
> > your system?
> to start i did osql -E in a command prompt, then I did CREATE DATABASE
> Study. Now I cant find the database in my hard drive. I'm "looking" for it
so
> i can use it in coldfusion server. I need to point to a physical file to
> register that db so I can manipulate it in my web pages.The documentation
on
> how to do such things arent very available on the ms knowledge base. At
least
> IMO
> Phil

Msde 2000 - Sql 2005 Express Upgrade Issue.

Hey, This is my first time posting here but here goes nothing...

Ok I upgraded an xp machine running to sql express 2005 by doing the inplace upgrade. The upgrade process went great, after the upgrade I could connect to the databases that had been upgraded using the management studio.

BUT.

When I try to connect to the databases using the third party software which had always worked in the past I get the error when trying to access from both the client and server machines.

[DBNETLIB][Connection open()).]SQL Server does not exist or access denied.

I then tried setting up SQL express 2005 on another xp station just to test how things worked if it wasn't an upgrade. I installed, attached the databases (which I copied to that local machine) and I was able to connect to them through the third party software from the server machine, but not client machines. The client machines gave me the same error as above.

Does anyone have any ideas, I have been talking to the third party support but haven't gotten any where yet... does anyone have any suggestions?

Thanks,why would you want to upgrade from MSDE 2000 to SQL 2005 express? Microsoft has stated more than 80% of the application running on SQL 2000 will not work on SQL 2005. Why not using the same old MSDE 2000?

most probably you will need to rewrite your application to handle SQL 2005|||I spoke with the third party software company and they assure me everything will work on sql express. We wanted to switch to sql express because it had the report server stuff built in. I don't really know that much about this stuff, can the sql 2005 express reporting stuff be run on msde ?|||I am not the expert here but I will just share what I have experienced so far.

Report server is a built in feature in SQL 2005. However, it has its limitation when it comes to report designer. My personal experience, it's easy to use, but it's not acceptable by the end user. I end up writing my own long script to output the whole report to excel file.

You shall show your users instead of simply pushing them to another technology. MSDE can run well on WinXP, so why change? If you can't give yourself a good reason to change, it's better to stick to something that's working.

Remember, free stuff, doesn't come in handy :D unless your requirement is very very simple.

If the software vendor assure you that, ask them to show you how to migrate the thing over. You can always use VMware or Parallels to do all the testing before you screw up your MSDE.|||Thanks for the insight with the reporting stuff. Do you know if the report stuff from express can be used with msde?

Also, I think it's to late for me on the screwing up the msde. I removed sql express now and I have reinstalled msde, but I am getting the same error I was getting with the express. I have done a little reading and it seems like it might be a problem with remote connections. Does anyone know how to make sure remote connections are allowed in msde ?sql

Msde 2000

This is my first time using SQL. I installed MSDE 2000 on my desktop and after restarting my PC I see an icon in the startup area MSSQLServer with the server being my T-Tag #.

I am trying to upsize my Access DB to Sqlserver. I am still confused as to where does this server reside? How does this whole thing work?

Also, when I tried to upsize my db I got an overflow error.

Could someone please explain how does this work?

Thanks,

DHYou really should have your instance name be one word with no special characters, so you might want to reinstall MSDE to start with.

The MSDE SQL Server can reside anywhere. A server is always preferrable. You just point to it in Access with ODBC or an Access Data Project.

Can you post the exact message you got on the upsize? This is probably an arithmetic overflow error, but who knows without seeing the error.|||Doesn't MSDE create a named instance by default?

Also, the poster is probably referring to the Tag # of the PC or a laptop, like Dell usually assignes to it's products, something like YG2PBF, so I don't see any problem with it.|||Doesn't MSDE create a named instance by default?

Also, the poster is probably referring to the Tag # of the PC or a laptop, like Dell usually assignes to it's products, something like YG2PBF, so I don't see any problem with it.

Yes, you are right. It uses the TTAG number of the desktop. The MSSQL icon in the start up area also had other names unser the serverl ist. Anyway, attached is the screen shot of the verflow error I encountered.|||Yes, you are right. It uses the TTAG number of the desktop. The MSSQL icon in the start up area also had other names unser the serverl ist. Anyway, attached is the screen shot of the verflow error I encountered.


OOps ..I forgot the attachment..

msde # of users allowed.

i have a questions concerning msde 2000.
1- how many user can access an msde database at one time?
(some resources say 5 some sau unlimited.)I believe it is 10|||You can find complete information here:
MSDE 2000 (http://www.microsoft.com/sql/techinfo/development/2000/MSDE2000.asp)
here is an excerpt from this page:
Performance
MSDE 2000 is a local data engine that can be shared. It has a managed concurrency workload governor that limits up to five concurrent batch workloads for optimal performance. Commands and log entries are available to monitor instances where more than five workloads are executed concurrently, a situation that can cause slower performance even on well-tuned systems. As more batch workloads are submitted beyond the five-workload limit, the concurrency governor continues to slow down the system. These workloads are not dropped or lost; they are still processed, but in an increasingly degraded performance mode. If your solution must support more than five concurrent workloads, it is highly recommended that you migrate to SQL Server 2000 or SQL Server 2000 Enterprise Edition for optimal performance at this higher level of scalability.

Hope this helps|||MSDE 1.0 (SQL 7) had a governor on the # of connections.

MSDE 2.0 (SQL 2k) just has a governor on concurrent processes.

so with MSDE 2.0, you can have 25 connections that stay open all the time-- and it works like a charm.

with MSDE 1.0, you would be going really slowly.

if you're asking 'is this the right solution for me'

i think that the answer is yes.

but you'll have to give us more information about your project before we can come to the correct diagnosis.

MSDE

I trying install MSDE 2000 for the first time on XP Sp2
When I try run setup it give error Instance name is invaild
only choice click ok. When I click it just goes away.
I now how do fix I just double clicking setup icon
Thanks for the help
hi Frank,
frank wrote:
> I trying install MSDE 2000 for the first time on XP Sp2
> When I try run setup it give error Instance name is invaild
> only choice click ok. When I click it just goes away.
> I now how do fix I just double clicking setup icon
>
> Thanks for the help
can you please post your command line you used to install MSDE?
MSDE must be installed using it's setup.exe boostrap installer, which
accepts (and requires) some parameters...
all usable parameters for installing a (somehow) customized MSDE are
available at
http://msdn.microsoft.com/library/de...stsql_84xl.asp
just for the case, I've just installed an MSDE named instance on a brand new
WinXP sp 2 machine...
I disabled the antivirus (it was Avast), checked "File & Printer Sharing"
was enabled, the "Server" service was running..
the LAN access was available through the subnetmask exception...
I installed a named instance like
setup.exe INSTANCENAME="MSDE" SAPWD=*** SECURITYMODE=SQL
DISABLENETWORKPROTOCOLS=0 /L*v "C:\MsdeLog.txt"
and that installed a named instance named "MSDE", allowing SQL Server
authenticated connections (mixed authentication), with support for remote
connections and logging the install process to C:\MsdeLog.txt, a text file
of about 2mb you can inspect for toubleshooting problems, searching for
RETURN VALUE 3
entries that denotate errors, where 10/20 lines before and/or after some
(somteime criptic) description of the problem is recoded... thi installation
worked as a charm... :D
after that I configured the Windows firewall defining an exception allowing
acces to the MSDE instance used TCP port and another exception for UDP 1434
port for the SQL Server Service Listener...
in order to configure XP sp2 for SQL Server connectivity you can ahave a
look at http://support.microsoft.com/default.aspx?kbid=841249
regards
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply