MSDE Release A max number of concurrent queries

Hi All. A friend of mine mentioned that Release A actually has the max number
of concurrent queries to be 25 instead of 7 as MSDE. Is this true? Thank you
hi Andrew,
Andrew @. Abaki wrote:
> Hi All. A friend of mine mentioned that Release A actually has the
> max number of concurrent queries to be 25 instead of 7 as MSDE. Is
> this true? Thank you
false.. MSDE (and there's only one of it, only different packages with
different eulas) allows up to 8 concurrent (of the ones included in the
count of the Governor it self) batches before the Governor Workload kicking
in ...
http://msdn.microsoft.com/library/?u...asp?frame=true
25 is a "magic number" guessed by Microsoft,
http://www.microsoft.com/sql/msde/ho.../msdeuse.mspx, at the question
Q. Can I use MSDE as a database for Web applications?
A. Yes, MSDE is an ideal solution for basic Web applications with up to 25
concurrent users.
this number obviously depends on the application code quality, access type,
data nature and design, activities on it, ...
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
|||The confusion comes from "concurrent queries" versus "concurrent users".
The workload governor operates off the former while users are typically
looking to configure based on the latter.
The workload governor allows essentially 480 (sub-second) database queries
or other (e.g., update) operations per minute without degradation. You can
ballpark what this means in terms of transactions. Assume a simple
transaction has perhaps 5 queries. A mid-level has perhaps 20, and a
complex transaction has about 40. So you can support between 10 and 100
transactions per minute with MSDE with no degradation. OLTP leans towards
the simple side (volume-wise you might have 70-80% of your transactions in
the simple category) so lets assume 75 transactions per minute.
The real question for MSDE thus is, how many users does it take to generate
75 transactions in a minute. If your users submit one transaction per
minute then you could support 75 users. If your users submit 2-3
transactions per minute then you get to the 25 users that Microsoft targets
as a maximum. If your workload leans towards the more complex transactions
then the numbers you support go down. If users do very infrequent
transactions then the numbers go up.
Microsoft's real target for MSDE was for apps that support 10 users or less.
There is a lot of history there in terms of the business target and the
technical requirements. One part of the requirements analysis dictated that
hard concurrent user limits cause major customer dissatisfaction. So MSDE
was not given a hard concurrent user limit nor was the governor set to make
performance fall off a cliff after 10 users. The result is that for many
applications MSDE supports far larger numbers of users than the technical
specs might indicate.
Hal Berenson, President
PredictableIT, LLC
www.predictableit.com
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3sbpn3Fn11hqU1@.individual.net...
> hi Andrew,
> Andrew @. Abaki wrote:
> false.. MSDE (and there's only one of it, only different packages with
> different eulas) allows up to 8 concurrent (of the ones included in the
> count of the Governor it self) batches before the Governor Workload
> kicking in ...
> http://msdn.microsoft.com/library/?u...asp?frame=true
> 25 is a "magic number" guessed by Microsoft,
> http://www.microsoft.com/sql/msde/ho.../msdeuse.mspx, at the question
> Q. Can I use MSDE as a database for Web applications?
> A. Yes, MSDE is an ideal solution for basic Web applications with up to 25
> concurrent users.
> this number obviously depends on the application code quality, access
> type, data nature and design, activities on it, ...
> --
> 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
>
|||And, BTW, this is an oversimplification. Most queries take a tiny fraction
of a second. So you could really support quite a bit more than I show. But
my example allows for some decent conservative planning.
Hal Berenson, President
PredictableIT, LLC
www.predictableit.com
"Hal Berenson" <hberenson@.predictableit.com> wrote in message
news:u9qGL4x2FHA.632@.TK2MSFTNGP10.phx.gbl...
> The confusion comes from "concurrent queries" versus "concurrent users".
> The workload governor operates off the former while users are typically
> looking to configure based on the latter.
> The workload governor allows essentially 480 (sub-second) database queries
> or other (e.g., update) operations per minute without degradation. You
> can ballpark what this means in terms of transactions. Assume a simple
> transaction has perhaps 5 queries. A mid-level has perhaps 20, and a
> complex transaction has about 40. So you can support between 10 and 100
> transactions per minute with MSDE with no degradation. OLTP leans towards
> the simple side (volume-wise you might have 70-80% of your transactions in
> the simple category) so lets assume 75 transactions per minute.
> The real question for MSDE thus is, how many users does it take to
> generate 75 transactions in a minute. If your users submit one
> transaction per minute then you could support 75 users. If your users
> submit 2-3 transactions per minute then you get to the 25 users that
> Microsoft targets as a maximum. If your workload leans towards the more
> complex transactions then the numbers you support go down. If users do
> very infrequent transactions then the numbers go up.
> Microsoft's real target for MSDE was for apps that support 10 users or
> less. There is a lot of history there in terms of the business target and
> the technical requirements. One part of the requirements analysis
> dictated that hard concurrent user limits cause major customer
> dissatisfaction. So MSDE was not given a hard concurrent user limit nor
> was the governor set to make performance fall off a cliff after 10 users.
> The result is that for many applications MSDE supports far larger numbers
> of users than the technical specs might indicate.
> Hal Berenson, President
> PredictableIT, LLC
> www.predictableit.com
>
> "Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
> news:3sbpn3Fn11hqU1@.individual.net...
>

MSDE Inatallation

Hi,
I downloaded the MSDE release A (MSDE2000A.exe) from below mentioned link.
http://www.microsoft.com/downloads/d...displaylang=en
Extracted the MSDE2000A.exe to local directory (C:\MSDERelA).
Through Command Prompt executed the following command:
setup SAPWD="sa" INSTANCENAME="Testdb" TARGETDIR="C:\MSDERelA" /L*v
"C:/MSDELog.log"
The following message is popedup:
"Please go to control panel to install adn configure system components"
if click ok, setup is aborted.
Note: My system have Windows XP operating system with Service pack 1
please help to properly install MSDE with the setup downloaded.
Regards,
Abdul Saleem
hi Abdhul,
Abdhul Saleem wrote:
> Hi,
> I downloaded the MSDE release A (MSDE2000A.exe) from below mentioned
> link.
> http://www.microsoft.com/downloads/d...displaylang=en
> Extracted the MSDE2000A.exe to local directory (C:\MSDERelA).
> Through Command Prompt executed the following command:
> setup SAPWD="sa" INSTANCENAME="Testdb" TARGETDIR="C:\MSDERelA" /L*v
> "C:/MSDELog.log"
> The following message is popedup:
> "Please go to control panel to install adn configure system
> components" if click ok, setup is aborted.
> Note: My system have Windows XP operating system with Service pack 1
> please help to properly install MSDE with the setup downloaded.
> Regards,
> Abdul Saleem
please verify File & Printer Sharing is enabled, the Server service up and
running too..
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 Error 18456

Hi,
Read a lot about the above mentioned error.
But I don't understand the solutions.
About the operating system I an a novice too.
Installed MSDE a few times before the server Icon with the green errow apered.
Deinstalled MSDE 2000 a few times and removed also the directories.
Some in this newsgroup mentioned that there are entries in the registry that
should be deleted. But about the registry I am a novice.
Is there another solution to make a clean install.
Henk
hi Henk,
Henk wrote:
> Hi,
> Read a lot about the above mentioned error.
> But I don't understand the solutions.
> About the operating system I an a novice too.
> Installed MSDE a few times before the server Icon with the green
> errow apered. Deinstalled MSDE 2000 a few times and removed also the
> directories.
> Some in this newsgroup mentioned that there are entries in the
> registry that should be deleted. But about the registry I am a novice.
> Is there another solution to make a clean install.
about the folders and registry entries to be deleted, you can have a look at
http://support.microsoft.com/default...EN-US;Q290991, which
completely remove an MSDE instance from a pc but for the presence orphaned
Windows Installer registry entries.. for the latter you have to use
MsiZap.exe, part of the Windows Installer SDK, as indicated in
http://support.microsoft.com/default...b;en-us;320873
unfortunately there's no other "manual" method to clean a system..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||"Andrea Montanari" schreef:
Knip
Thank you Andrea,
Your suggestion helped me a lot.
But I can't connect to the database.
I like to connect a database with Visual basic.net (standard) trhough a
sql data adaptor,wich invokes a wizard.
I choose New. connection.
Servername=PC_name
Login = Username
Passw = Userlogin passw
The next error appeared.
Login Failed for user.
What I am doing wrong.
Sorry but I am a novice and a little bit slow in understanding.
Henk.
|||hi Henk,
Henk wrote:
> But I can't connect to the database.
> I like to connect a database with Visual basic.net (standard) trhough
> a sql data adaptor,wich invokes a wizard.
> I choose New. connection.
> Servername=PC_name
> Login = Username
> Passw = Userlogin passw
> The next error appeared.
> Login Failed for user.
> What I am doing wrong.
> Sorry but I am a novice and a little bit slow in understanding.
i hope the exception raised continue with " .. not associated with a trusted
SQL Server connection"
if this is the case you have to understand that MSDE installs by default on
WinNT platform enabling only trusted authenticated connections..
you can modify this behaviour both at install time, providing the
SECURITYMODE=SQL parameter to the setup.exe MSDE boostrap installer, or
later, at run-time, accessing the Windows registry and modifying the
HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer
LoginMode=2
for a default MSDE instance, or
HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\InstanceName\MSSQLServer
LoginMode=2
for a named instance...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||"Andrea Montanari" schreef:

> hi Henk,
> Henk wrote:
> i hope the exception raised continue with " .. not associated with a trusted
> SQL Server connection"
> if this is the case you have to understand that MSDE installs by default on
> WinNT platform enabling only trusted authenticated connections..
> you can modify this behaviour both at install time, providing the
> SECURITYMODE=SQL parameter to the setup.exe MSDE boostrap installer, or
> later, at run-time, accessing the Windows registry and modifying the
> HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer
> LoginMode=2
> for a default MSDE instance, or
> HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\InstanceName\MSSQLServer
> LoginMode=2
> for a named instance...
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
>Thanks for your quick reply.
I am not used to change any thing in the registry.
I found the next entrys.
Defaultlogin Reg_SZ guest
Loginmode Reg_Dword 0X00000000(0)
Should I Change 0X00000000(0) into 2
But during setup I gave the next parameter in: SecurityMode=SQL
Henk.
|||"Henk" schreef:

>
> "Andrea Montanari" schreef:
>
> I am not used to change any thing in the registry.
> I found the next entrys.
> Defaultlogin Reg_SZ guest
> Loginmode Reg_Dword 0X00000000(0)
> Should I Change 0X00000000(0) into 2
> But during setup I gave the next parameter in: SecurityMode=SQL
> Henk.
>
I tried the above mentioned settings.
But nothing worked.
Tried the next thing.
Removed MSDE2000 through
Start-Config-Software-MicrosoftSQLMSDe
Removed
Restart
Manually removed Map Microsoft SQL Server
within map MSSQl
Map-Log
New install MSDE200
Installed MSDERelA
setup SAPWD=Sapassword SecurityMode=SQL
Restart
Server Runs
Registery check
Loginmode=0
DefaultLogin = guest.
Manually Loginmode=2 changed
Tried again in VB.net
Login failed for user.
I tried everything but nothing works.
Henk
|||hi,
Henk wrote:
> I tried the above mentioned settings.
> But nothing worked.
> Tried the next thing.
> Removed MSDE2000 through
> Start-Config-Software-MicrosoftSQLMSDe
> Removed
> Restart
> Manually removed Map Microsoft SQL Server
> within map MSSQl
> Map-Log
> New install MSDE200
> Installed MSDERelA
> setup SAPWD=Sapassword SecurityMode=SQL
> Restart
> Server Runs
> Registery check
> Loginmode=0
> DefaultLogin = guest.
> Manually Loginmode=2 changed
> Tried again in VB.net
> Login failed for user.
> I tried everything but nothing works.
first... try SECURITYMODE=SQL ... perhaps it's case sensitive.. never
tried mixed case...
then... if you modify the registry try stopping and restarting the server...
then.. can you please repeat the exception you are prompted with?
thank you
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||"Andrea Montanari" schreef:

> hi,
> Henk wrote:
> first... try SECURITYMODE=SQL ... perhaps it's case sensitive.. never
> tried mixed case...
> then... if you modify the registry try stopping and restarting the server...
> then.. can you please repeat the exception you are prompted with?
> thank you
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
Many thanks again for answering my questions.
But none of the answers solved the question.
But after all it works.
What I have done is the following.
Deinstalled MSDE.
Removed everything with SQL from program files and from the registery.
Dit a registery cleanup, with RegClean.
And after all defragmented my harddisk.
After that I installed MSDE and started to ad a sqladapter and everything
works.
I scrolled through the started services and there was one thing that seemed
to be different, the SQLServerAgent was automaticly started.
Till now I don't know what i dit wrong and that is a shame, but it works.
Thanks again for answering.
Henk

>