Connection Limit of express's reporting services

Hi,
Do you know the connection limit of express's reporting services?
As i know standard's version is unlimited, so how about the adv version.
Can I use this free version as web reporting tool for more than 100 users?
Many Thanks....Hi,
yes, you have no query governor anymore, but you are restricted to the
hardware limitations of SQL Server Express, so scaling up with Express
is limited. There are also no connection limitations.
HTH, Jens K. Suessmeyer.
--
http://www.sqlserver2005.de
--|||Hi Jens,
Thanks.
Do you have any benchmarking info between express & standard in term of RS
performance (no db installed in express) where express only support One CPU
& allocate 1G Mem.
What I want to know how RS consume server resources so i can make a decision
to choose express RS or standard RS for my web report which will support 100
users.
Many thanks again.
"Jens" <Jens@.sqlserver2005.de> wrote in message
news:1169538427.949486.105720@.v45g2000cwv.googlegroups.com...
> Hi,
> yes, you have no query governor anymore, but you are restricted to the
> hardware limitations of SQL Server Express, so scaling up with Express
> is limited. There are also no connection limitations.
> HTH, Jens K. Suessmeyer.
> --
> http://www.sqlserver2005.de
> --
>|||Hi,
this is really hard to tell, there is no rule of thumb as it has many
influencing factors. What about processing time for the reports, how
often do they access the reports, how big are the reports, which
reporting format will they produce, etc. You will have to run a load
test on the machine to see how your report are performing for getting a
performance measure to scale you machine.
HTH, Jens K. Suessmeyer.
--
http://www.sqlserver2005.de
--|||Thanks jens, will try and test.
"Jens" <Jens@.sqlserver2005.de> wrote in message
news:1169584143.023207.298610@.j27g2000cwj.googlegroups.com...
> Hi,
> this is really hard to tell, there is no rule of thumb as it has many
> influencing factors. What about processing time for the reports, how
> often do they access the reports, how big are the reports, which
> reporting format will they produce, etc. You will have to run a load
> test on the machine to see how your report are performing for getting a
> performance measure to scale you machine.
>
> HTH, Jens K. Suessmeyer.
> --
> http://www.sqlserver2005.de
> --
>

Connection Issues To Report Services

Hello all,

I just installed the SQL 2k5 standard suite of services on a w2k3 enterprise edition server. All went well except for the connection to the reporting server. I get the error below.

"No connection could be made because the target machine actively refused it"

I can't seem to find any information on this error and have no clue where to even start. I've done 10+ installations of this software on various machines and have not encountered this error on any of them.

I have uninstalled, then reinstalled the reporting services and still no solution. All connection attempts are being made on the actual server, not from a desktop. sp1 for sql 2k5 is also installed, if that helps.

Windows Firewall is off.

What web searches I've done have turned up nothing useful. I'm pretty good at figuring this stuff out but this error provides very little of any use.

Anyone out there have any ideas?

Thanks in advance,

Greg

Have you seen this page: http://www.sqljunkies.com/WebLog/edwardm/ ?|||

First, thanks for the link. I'll make note of the ports used by SSAS and some of the other information in there.

I did figure this out, though. Not a very scientific approach so I'll have to run into this problem again to verify but, at a minimum, backing up the encryption key from within Reporting Services Configuration seemed to do the trick. I had a few other things out of whack, too.

At one point, the Backup option was disabled, but disabling "Web Server and HTTP Access" via SQL Server Surface Area Configuration -> Surface Area Configuration for Feature -> Reporting Services enabled the Backup button (kind of a round-about way of making that happen).

After backing up the encryption key, I enabled that option and could connect after that. Problem Solved!

This was further complicated by the fact that the reporting services install didn't conform to some "default" system configuration and performed only a "files-only" install. I really didn't pay that much attention during the install and the difference never really registered in my mind. So, I had to manually configure the reporting server (web directories, db connections, dbs and all).

So, chalk this up to experience and I'll know the next time I run into this.

Other things I addressed, but I'm not sure were relevant were:

the state of the IIS Admin and WWW publishing services (these were stopped and in manual mode during the install - I would think the install would start these if needed)

The execution permissions and application protection modes of the reporting server virtual directories (these were different on the problem installation than a "default" installation - an install on another machine that did work fine)

I don't think I needed to do the reporting services re-install.

When creating the databases manually, I ended up having to do that with scripts. For some reason, the database creation was timing out. The creation of the two databases was ok, but the reporting server temp db did not have any objects in it (no tables, views, etc).

There are a myriad of other things, but I'm almost certain these weren't relevant. All-in-all, a hassle.

Greg

|||Greg: Thanks for your post. I have a problem getting SSRS to work on one of my servers, too. I posted on Sunday:
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1215786&SiteID=1
but no one answered. In my case, the local SSRS does not even appear in the list of servers to initialize, within the RS Config Manager. When I installed SSRS, I got the message "Reporting Services was installed, but not configured". This was on a reinstall of SQL05 needed to place the files on a drive other than C:

I will see if backing up the key fixes my problem, next time I'm at that site.|||I'm back at the server with the problem. When I run RS Config Mgr, the button to back up the encryption key is disabled. The only enabled buttons on that page are the 'Restore' button, and the 'Delete' (delete encrypted content) button.

I tried disabling HTTP and Web Access using the Surface Area tool, but the 'Backup' button is still disabled.

Any ideas on how to diagnose and fix this?|||

Hmm. That's what I did. One other thing you might try is deleting the encrypted content. At some point in my troubleshooting process, I pressed that button. I would assume that if encrypted content did exist, and you didn't have the proper encryption key to restore from, the encrypted content would be un-accessible (that's rather obvious). I was comfortable deleting encrypted content because the installation was new and there was nothing to lose.

After doing that, you could then go throught the HTTP and Web Access routine again.

|||No luck for me. Could not get the 'Backup' button enabled on the Encryption Key page. I found in the event log I'm getting EventID 7000 from the RS Service saying "...cannot connect to the report server database". I tried scripting out the DB creation and running that separately. The script ran without errors, but I still get the connection failure event.

I tried running "rsconfig.exe -t -c -d SSRS -a windows -s mssqlserver", where SSRS is my RS db name and mssqlserver is the SQL Server instance name (the default instance), and it came back with "The command completed successfully"

Now since running rsconfig, in the GUI version, RS Configuration Mgr, I'm getting error popups saying it can't connect to SQL Server at all. The popups say it was trying to connect using named pipes. I went to the Surface Area tool and enabled named pipes on remote connections, but RS Config Mgr still can't connect.

It seems like my installation is hosed. I thought Crystal Enterprise was hard to use, but this SSRS is worse! I'm open to suggestions. Does anyone know a reliable way to configure the db connection for Reporting Services?|||I uninstalled and reinstalled the Reporting Services components. This at least allowed RS Config Mgr to connect to SQL Server. However, when I attempt to create a new database for RS, each step succeeds except the last one. For the "Setting Connection Info for the Reporting Server" task, there

was a yellow '!', with the explanation, "Although saving the database

connection succeeded, the report server cannot access internal

information about this deployment to determine if the current

configuration is valid for this edition. ..." The RS Service is still logging errors in the event log saying it cannot connect. I give up.

connection issue with enterprise manager but works with management studio

Hi,

I have an interesting scenario.

I have a SQL Server 2000 Standard Edition instance running on Computer A. I'm trying to access it through computers B and C.

Computer B has Sql Server 2005 Express Edition installed and I was able to use its Management Studio and
connect to instance on Computer A.

Computer C has SQL Server 2000 Standard Edition installed. When I try to connect to the instance on Computer A,
I get connection failed message.

I checked some settings. Both TCP/IP and Named pipes are enabled on the instance in A. The TCP/IP port is set to 1433 for
both client and server.

Please give me some ideas as to how I can solve this problem.

-Thanks

What is the error message that is displayed?|||I am assuming all three are on the same network then it is a simple right click at the top of Management Studio and register the 2000 then it becomes local to you. I have registered 68 7/2000 in one box so it works . Hope this helps.|||

The error said something like

Invalid Connection.ConnetionOpen(Invalid Instance)

|||

I figured it out.

Both A and C had Sql Server 2000 instances. When you try to connect to one Sql Server 2000 instance from another, Enterprise Manager automatically sets "Dynamically determine port" option and hence the connection fails. What you can do is use the Client Network Utility in C and create a new TCP/IP alias and uncheck the "dynamically determine port" option and manually set it to 1433. Then u can use Enterprise Manager in C and select the new alias that you created and finish registering the 2000 instance from A.

Thanks for your replies.

|||

shiversticks:

I figured it out.

Both A and C had Sql Server 2000 instances. When you try to connect to one Sql Server 2000 instance from another, Enterprise Manager automatically sets "Dynamically determine port" option and hence the connection fails. What you can do is use the Client Network Utility in C and create a new TCP/IP alias and uncheck the "dynamically determine port" option and manually set it to 1433. Then u can use Enterprise Manager in C and select the new alias that you created and finish registering the 2000 instance from A.

Thanks for your replies.

(on the same network then it is a simple right click at the top of Management Studio and register the 2000 then it becomes local to you. I have registered 68 7/2000 in one box so it works )

For the reference of future readers of this thread you just right click and register the other SQL Server as I originally posted and leave your port setings alone in eigth years I have not had reason to touch port settings it is not needed. Port settings could lead to SQL injection attacks.

Connection is busy with results for another hstmt

HI guys,

I'm using ODBC driver from WinXP SP2 with SQL Server 2005 Express (on my machine for test) and SQL Server 2005 Standard (on the production machine).

With SQL Server 2005 Express I've no problem, but with SQL Server 2005 Standard, in some query, I get "Connection is busy with results for another hstmt".

I'm working with VisualStudio 2003 with standard CDatabase and CRecordSet MFC classes.

I looked for an advice in the Microsoft KB but I found only Service Pack for SQL Server 2000 !

Everything could be useful !

Thanks a lot!

Bye, Domenico

You can avoid this error message by switching to the SQL Server 2005 ODBC driver, 'SQL Native Client' and enabling the MARS (Multiple Active Result Sets feature). There is more information in Books Online and also here http://blogs.msdn.com/dataaccess/archive/2005/08/02/446894.aspx