We're running on an AMD 8-core Opteron, with Enterprise RS 2005 64-bit.
It seems that when we have multiple users running reports at the same time,
the mdx queries get executed in parallel to the AS database, but the
processing of the data by reporting services is done in a single-thread mode.
E.g. a report run by itself takes 15 seconds. Same report run by 5 people can
take 3:30 to return (with the w3wp taking up the equivalent of only 1 core).
My laptop running RS 2005 processes these simultaneous report faster than our
Opteron!!!
We played with setting the # of workers on the IIS Appl Pool, and it does
seem to cause multiple reports to be processed simultaneously, but I don't
think this is the best solution. I think we are running the equivalent of 8
copies of reporting services on the box in this configuration -- I see 8 RS
logs being generated.
Is there a setting in either IIS or RS 2005 to make it process requests in
parallel?
SteveHi Steve,
Me too, interested to know the answer to your question. If you find out -
please update.
Thanks,
Al
"SteveIrwin" wrote:
...
> Is there a setting in either IIS or RS 2005 to make it process requests in
> parallel?
> Steve|||It looks like the App Pool that gets created for RS has CPUAffinity assign to
it, I think. When you create another App Pool in IIS, and switch the
Reporting Services vdir to use the new pool, then it behaves like a regular
website -- one worker process that answers all requests that come to it,
spawning multiple threads if necessary.
So it comes down to how you want to have RS to work: do you want one worker
that spawns threads to handle requests, or have multiple workers that will
each take up only one cpu/core for each request, then move on to the next
request. It would be interested to see any whitepapers on this subject.
Steve
"TheTechie" wrote:
> Hi Steve,
> Me too, interested to know the answer to your question. If you find out -
> please update.
> Thanks,
> Al
> "SteveIrwin" wrote:
> ...
> > Is there a setting in either IIS or RS 2005 to make it process requests in
> > parallel?
> >
> > Steve
Showing posts with label users. Show all posts
Showing posts with label users. Show all posts
Tuesday, March 6, 2012
Thursday, February 16, 2012
5 User License
Hi,
What exactly does the 5 user(s) license of MSDE means?
"sa" is a user and i can have only 4 more users, does that means total 5
users license?
Or its the number of users connected to MSDE at any given point of time?
Reetesh.
hi Reetesh,
"Reetesh B. Chhatpar" <reetesh@.widesystems.com> ha scritto nel
messaggio news:OZsTAvI1EHA.1408@.TK2MSFTNGP10.phx.gbl
> Hi,
> What exactly does the 5 user(s) license of MSDE means?
> "sa" is a user and i can have only 4 more users, does that means
> total 5 users license?
> Or its the number of users connected to MSDE at any given point of
> time?
> Reetesh.
MSDE does not have a "5 users license" limitation... MSDE includes a
Governor Workloads that kicks in when 8 of more concurrent workloads
activities (batches that include the operations as described in
http://msdn.microsoft.com/library/?u...asp?frame=true)
are executed and slows all of them down, but more workloads are supported
and only slowed down...
AFAIK, no such a limitation exists, nor technical or legal..
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
|||Hi Andrea,
The article was really worth reading. Thanks for clearing up my doubt for
MSDE. Could you also please share with me the licensing logic for SQL
Server. How do i cut-cost my product installation when I choose backend as
SQL?
Reetesh B. Chhatpar
ShawMan Software Enterprises
www.shawmansoftware.com
Diamond is just another piece of coal that did well under pressure.
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:30rjstF346j3iU1@.uni-berlin.de...
> hi Reetesh,
> "Reetesh B. Chhatpar" <reetesh@.widesystems.com> ha scritto nel
> messaggio news:OZsTAvI1EHA.1408@.TK2MSFTNGP10.phx.gbl
> MSDE does not have a "5 users license" limitation... MSDE includes a
> Governor Workloads that kicks in when 8 of more concurrent workloads
> activities (batches that include the operations as described in
>
http://msdn.microsoft.com/library/?u...asp?frame=true)
> are executed and slows all of them down, but more workloads are supported
> and only slowed down...
> AFAIK, no such a limitation exists, nor technical or legal..
> --
> 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
>
|||hi Reetesh,
"Reetesh B. Chhatpar" <reetesh@.widesystems.com> ha scritto nel
messaggio news:%230kNRzQ1EHA.2540@.TK2MSFTNGP09.phx.gbl
> Hi Andrea,
> The article was really worth reading. Thanks for clearing up my doubt
> for MSDE. Could you also please share with me the licensing logic for
> SQL Server. How do i cut-cost my product installation when I choose
> backend as SQL?
in order to optimze your license fees, perhaps you've better have a call
with a Microsoft representative, as this really is a big deal and i'm not a
lawyer :D
if you choose MSDE (as per MSDE Release A package), your only need is to
register for distribution
(http://www.microsoft.com/sql/msde/ho...stregister.asp) , no other
requirement is necessary, for you nor for your customers... theoretical max
number of simultaneos connections stays at 32767 but, at 8 concurrent
workloads the Governor will kick in...
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
What exactly does the 5 user(s) license of MSDE means?
"sa" is a user and i can have only 4 more users, does that means total 5
users license?
Or its the number of users connected to MSDE at any given point of time?
Reetesh.
hi Reetesh,
"Reetesh B. Chhatpar" <reetesh@.widesystems.com> ha scritto nel
messaggio news:OZsTAvI1EHA.1408@.TK2MSFTNGP10.phx.gbl
> Hi,
> What exactly does the 5 user(s) license of MSDE means?
> "sa" is a user and i can have only 4 more users, does that means
> total 5 users license?
> Or its the number of users connected to MSDE at any given point of
> time?
> Reetesh.
MSDE does not have a "5 users license" limitation... MSDE includes a
Governor Workloads that kicks in when 8 of more concurrent workloads
activities (batches that include the operations as described in
http://msdn.microsoft.com/library/?u...asp?frame=true)
are executed and slows all of them down, but more workloads are supported
and only slowed down...
AFAIK, no such a limitation exists, nor technical or legal..
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
|||Hi Andrea,
The article was really worth reading. Thanks for clearing up my doubt for
MSDE. Could you also please share with me the licensing logic for SQL
Server. How do i cut-cost my product installation when I choose backend as
SQL?
Reetesh B. Chhatpar
ShawMan Software Enterprises
www.shawmansoftware.com
Diamond is just another piece of coal that did well under pressure.
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:30rjstF346j3iU1@.uni-berlin.de...
> hi Reetesh,
> "Reetesh B. Chhatpar" <reetesh@.widesystems.com> ha scritto nel
> messaggio news:OZsTAvI1EHA.1408@.TK2MSFTNGP10.phx.gbl
> MSDE does not have a "5 users license" limitation... MSDE includes a
> Governor Workloads that kicks in when 8 of more concurrent workloads
> activities (batches that include the operations as described in
>
http://msdn.microsoft.com/library/?u...asp?frame=true)
> are executed and slows all of them down, but more workloads are supported
> and only slowed down...
> AFAIK, no such a limitation exists, nor technical or legal..
> --
> 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
>
|||hi Reetesh,
"Reetesh B. Chhatpar" <reetesh@.widesystems.com> ha scritto nel
messaggio news:%230kNRzQ1EHA.2540@.TK2MSFTNGP09.phx.gbl
> Hi Andrea,
> The article was really worth reading. Thanks for clearing up my doubt
> for MSDE. Could you also please share with me the licensing logic for
> SQL Server. How do i cut-cost my product installation when I choose
> backend as SQL?
in order to optimze your license fees, perhaps you've better have a call
with a Microsoft representative, as this really is a big deal and i'm not a
lawyer :D
if you choose MSDE (as per MSDE Release A package), your only need is to
register for distribution
(http://www.microsoft.com/sql/msde/ho...stregister.asp) , no other
requirement is necessary, for you nor for your customers... theoretical max
number of simultaneos connections stays at 32767 but, at 8 concurrent
workloads the Governor will kick in...
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
Saturday, February 11, 2012
3-way replication?
Hello,
I currently have a database set up for replication on 3 servers as
follows:
Pub - users connect and update database
Sub1 - database is accessed for local application
Sub2 - database is accessed for local application
The subscriptions are set up for both immediate and queued updating, so,
in theory, if Pub goes down, the users can re-connect to Sub1 to update
the database, and when Pub comes back, the queued updating will apply
the changes to Pub. Also, during the time Pub is down, the local
application on Sub1 will have access to current data.
However, as I understand it, Sub2 will not have access to the latest
data while Pub is down, since the only way those changes make it to Sub2
is through Pub. So, Sub2 will be accessing "old" data as long as Pub is
unable to send the changes.
Do I have this right ? Is there a simple way to get Sub1 to update Sub2
when Pub is down ? As it is now configured, it's kind of a pain in the
neck to manage the replication when we have to make a change to the
database definition, and I also want people to be able to update at Sub2
and have the changes propagate to Sub1 and Pub, in the event that
becomes necessary. But I don't want to create a structure that is a
nightmare to manage.
Any suggestions ?
Thanks,
Patrick
No, there is no simple way to do this.
Replication requires a publisher which figures out what goes where.
What you could do is have Pub publish to Sub1, and then have Sub1 publish to
Sub2. I would use merge replication for this.
Why are you using immediate updating?
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Patrick Johnson" <PJohnson_TechnoScope@.nospam.com> wrote in message
news:PJohnson_TechnoScope-09A593.15383717022005@.msnews.microsoft.com...
> Hello,
> I currently have a database set up for replication on 3 servers as
> follows:
> Pub - users connect and update database
> Sub1 - database is accessed for local application
> Sub2 - database is accessed for local application
> The subscriptions are set up for both immediate and queued updating, so,
> in theory, if Pub goes down, the users can re-connect to Sub1 to update
> the database, and when Pub comes back, the queued updating will apply
> the changes to Pub. Also, during the time Pub is down, the local
> application on Sub1 will have access to current data.
> However, as I understand it, Sub2 will not have access to the latest
> data while Pub is down, since the only way those changes make it to Sub2
> is through Pub. So, Sub2 will be accessing "old" data as long as Pub is
> unable to send the changes.
> Do I have this right ? Is there a simple way to get Sub1 to update Sub2
> when Pub is down ? As it is now configured, it's kind of a pain in the
> neck to manage the replication when we have to make a change to the
> database definition, and I also want people to be able to update at Sub2
> and have the changes propagate to Sub1 and Pub, in the event that
> becomes necessary. But I don't want to create a structure that is a
> nightmare to manage.
> Any suggestions ?
> Thanks,
> Patrick
|||In article <uHp4mjTFFHA.1264@.TK2MSFTNGP12.phx.gbl>,
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote:
> No, there is no simple way to do this.
> Replication requires a publisher which figures out what goes where.
> What you could do is have Pub publish to Sub1, and then have Sub1 publish to
> Sub2. I would use merge replication for this.
> Why are you using immediate updating?
Hi Hilary,
Thanks for your reply.
I have all of the users updating at Pub right now, so conceivably I
could get away without immediate updating, but the intent is that local
updates can be made at Sub1 and Sub2 and propagated immediately through
the system.
In practice it is a rare event for an update to happen someplace other
than at Pub.
Is immediate updating a bad idea ?
It's been a while since I set it up, but I remember there was some
reason I didn't want to use merge. Of course, now I can't remember what
it was.
Thanks,
Patrick
I currently have a database set up for replication on 3 servers as
follows:
Pub - users connect and update database
Sub1 - database is accessed for local application
Sub2 - database is accessed for local application
The subscriptions are set up for both immediate and queued updating, so,
in theory, if Pub goes down, the users can re-connect to Sub1 to update
the database, and when Pub comes back, the queued updating will apply
the changes to Pub. Also, during the time Pub is down, the local
application on Sub1 will have access to current data.
However, as I understand it, Sub2 will not have access to the latest
data while Pub is down, since the only way those changes make it to Sub2
is through Pub. So, Sub2 will be accessing "old" data as long as Pub is
unable to send the changes.
Do I have this right ? Is there a simple way to get Sub1 to update Sub2
when Pub is down ? As it is now configured, it's kind of a pain in the
neck to manage the replication when we have to make a change to the
database definition, and I also want people to be able to update at Sub2
and have the changes propagate to Sub1 and Pub, in the event that
becomes necessary. But I don't want to create a structure that is a
nightmare to manage.
Any suggestions ?
Thanks,
Patrick
No, there is no simple way to do this.
Replication requires a publisher which figures out what goes where.
What you could do is have Pub publish to Sub1, and then have Sub1 publish to
Sub2. I would use merge replication for this.
Why are you using immediate updating?
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Patrick Johnson" <PJohnson_TechnoScope@.nospam.com> wrote in message
news:PJohnson_TechnoScope-09A593.15383717022005@.msnews.microsoft.com...
> Hello,
> I currently have a database set up for replication on 3 servers as
> follows:
> Pub - users connect and update database
> Sub1 - database is accessed for local application
> Sub2 - database is accessed for local application
> The subscriptions are set up for both immediate and queued updating, so,
> in theory, if Pub goes down, the users can re-connect to Sub1 to update
> the database, and when Pub comes back, the queued updating will apply
> the changes to Pub. Also, during the time Pub is down, the local
> application on Sub1 will have access to current data.
> However, as I understand it, Sub2 will not have access to the latest
> data while Pub is down, since the only way those changes make it to Sub2
> is through Pub. So, Sub2 will be accessing "old" data as long as Pub is
> unable to send the changes.
> Do I have this right ? Is there a simple way to get Sub1 to update Sub2
> when Pub is down ? As it is now configured, it's kind of a pain in the
> neck to manage the replication when we have to make a change to the
> database definition, and I also want people to be able to update at Sub2
> and have the changes propagate to Sub1 and Pub, in the event that
> becomes necessary. But I don't want to create a structure that is a
> nightmare to manage.
> Any suggestions ?
> Thanks,
> Patrick
|||In article <uHp4mjTFFHA.1264@.TK2MSFTNGP12.phx.gbl>,
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote:
> No, there is no simple way to do this.
> Replication requires a publisher which figures out what goes where.
> What you could do is have Pub publish to Sub1, and then have Sub1 publish to
> Sub2. I would use merge replication for this.
> Why are you using immediate updating?
Hi Hilary,
Thanks for your reply.
I have all of the users updating at Pub right now, so conceivably I
could get away without immediate updating, but the intent is that local
updates can be made at Sub1 and Sub2 and propagated immediately through
the system.
In practice it is a rare event for an update to happen someplace other
than at Pub.
Is immediate updating a bad idea ?
It's been a while since I set it up, but I remember there was some
reason I didn't want to use merge. Of course, now I can't remember what
it was.
Thanks,
Patrick
Labels:
3-way,
accessed,
asfollowspub,
connect,
database,
databasesub1,
microsoft,
mysql,
oracle,
replication,
server,
servers,
sql,
update,
users
3rd-party report editors
Does anyone know of any products out there that allow end users to control the layout and fields of a report without having to install any special software on their machine?SQL 2005 has a web-based Report Builder which may do the trick for you.
SQL 2000 + Panorama Enterprise Report Builder is another option.|||You could also try ActiveReports by Data Dynamics - http://www.datadynamics.com/Products/ProductOverview.aspx?Product=ARNET2. It integrates very smoothly with .NET programs, and all the DLLs can be redistributed for free (vs. Crystal where design components require a per-seat license). Not quite as slick as Crystal or Reporting Services, but the cost and flexibility make it worth looking into.
SQL 2000 + Panorama Enterprise Report Builder is another option.|||You could also try ActiveReports by Data Dynamics - http://www.datadynamics.com/Products/ProductOverview.aspx?Product=ARNET2. It integrates very smoothly with .NET programs, and all the DLLs can be redistributed for free (vs. Crystal where design components require a per-seat license). Not quite as slick as Crystal or Reporting Services, but the cost and flexibility make it worth looking into.
josh|||Hi Josh,
I looked into ActiveReports and while it did look promising it seems the end-user designer only applies to WinForms.
Thanks for the suggestion, though.
Subscribe to:
Posts (Atom)