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 max field size?

Hi,
I have MSDE installed on my computer and I'm usingWeb Data Administrator to manage my databses. The problem is that whenever I add a column with a length of more than 8000, I get the following error:
Length must be between 0 and 8000
If I create the column programmatically then i get this error:
The following error occured while executing the query:
Server: Msg 131, Level 15, State 2, Line 2
The size (8005) given to the column 'Article' exceeds the maximum allowed for any data type (8000).
I need several columns that can hold around32,000 characters. What's the deal? Is this a limit with MSDE, or am Imissing something?
Thanks

::Is this a limit with MSDE, or am I missing something?

Yoou miss reading the documentation.

ROWS in SQL Server - not just MSDE - are limited to 8000 bytes. This means the whole row, not a single field.

For longer data there are special datatypes (like text or ntext) that do not store the data in the row, but use separate tables. They are limited (no indexing and some other limitations).They work wonderfully with up to 2gb per field.

This is properly documented in the documentation for SQL Server, which I suggest you ahve a look at. It is also available online at Microsoft.

|||

The documentation to which thona is referring (but for which he never provides a link) is calledSQL Server 2000 Books Online. It is a free reference from Microsoft and is one which I personally refer to many times a day. It is a large download but well worth the time.

The same content is available at the MSDN site:Getting Started with SQL Server Books Online.

|||What Sql Server datatype would give me the equivalent of the "Memo" type in Access?
Thanks
|||That would be text (or ntext if you need to support international characters).
|||I'm sorry, but I should have asked this in my previous post...
What length should I specify?
Like... text(16), or text(32)?
Am I correct in assuming that (16) would give me 32768 characters?
Thanx
|||

stevesimon wrote:

I'm sorry, but I should have asked this in my previous post...
What length should I specify?
Like... text(16), or text(32)?
Am I correct in assuming that (16) would give me 32768 characters?
Thanx

I wouldn't specify a length at all -- it is not needed for the text data type.
As suggested, Books Online and MSDN are excellent references and youcould easily find this information yourself. According tontext, text, and image the text data type can store 2,147,483,647 characters.
|||

Just a qwuestion -why are you so reluctant to even LOOK into the online documentation ONCE?

Btw, tehe equivalent of Access "Memo" is NOT text - it is ntext. Access has no notion of non-unicode strings.

|||I did look at the documentation, but could not find the answer to my specific question.
|||Try using OLE(Object Linking and Embedding) in Access to store them asWord and import them into MSDE as image files and most of your problemswill go away. Hope this helps.
Kind regards,
Gift Peddie

MSDE Max Connections?

Hi, can anyone tell me whats the maximum number of connections you can have to MSDE? Eg, is it enough to host an intranet site for a relativly small business?There is no practical maximum. There is a throttle, however, when there are more than five concurrent sessions that are processing data. I've seen apps with many dozens of users use MSDE without the throttle kick in, when their data usage was relatively light.

There are lots of subtleties, but it's a good chance that it'll work for you.

Don|||Thanks Don :)