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 Failure to SQL Server 2005

I am trying to connect to a SQL Server 2005 instance from another machine
using Query Analyzer (SQL Server 2000 version) and I am getting the following
error:
Server: Msg 11, Level 16, State 1
[Microsoft][ODBC SQL Server Driver][DBNETLIB]General network error.
I can connect to other SQL Server 2000 versions but not the 2005.
Thanks
Allen
Did you enable the Allow Remote Connections option for the SQL2005 server
instance?
Andrew J. Kelly SQL MVP
"Allen" <Allen@.discussions.microsoft.com> wrote in message
news:7F4792F3-8931-4E92-BEDA-0058D9917CFD@.microsoft.com...
>I am trying to connect to a SQL Server 2005 instance from another machine
> using Query Analyzer (SQL Server 2000 version) and I am getting the
> following
> error:
> Server: Msg 11, Level 16, State 1
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]General network error.
> I can connect to other SQL Server 2000 versions but not the 2005.
> Thanks
> --
> Allen

Connection Failure to SQL Server 2005

I am trying to connect to a SQL Server 2005 instance from another machine
using Query Analyzer (SQL Server 2000 version) and I am getting the followin
g
error:
Server: Msg 11, Level 16, State 1
[Microsoft][ODBC SQL Server Driver][DBNETLIB]General network err
or.
I can connect to other SQL Server 2000 versions but not the 2005.
Thanks
--
AllenDid you enable the Allow Remote Connections option for the SQL2005 server
instance?
Andrew J. Kelly SQL MVP
"Allen" <Allen@.discussions.microsoft.com> wrote in message
news:7F4792F3-8931-4E92-BEDA-0058D9917CFD@.microsoft.com...
>I am trying to connect to a SQL Server 2005 instance from another machine
> using Query Analyzer (SQL Server 2000 version) and I am getting the
> following
> error:
> Server: Msg 11, Level 16, State 1
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]General network e
rror.
> I can connect to other SQL Server 2000 versions but not the 2005.
> Thanks
> --
> Allen|||I've serched high and low for this facility and cannot find it.
I have enabled both client/server tcp/ip named pipes shared memory
and still cannot connect.
"Andrew J. Kelly" wrote:

> Did you enable the Allow Remote Connections option for the SQL2005 server
> instance?
> --
> Andrew J. Kelly SQL MVP
>
> "Allen" <Allen@.discussions.microsoft.com> wrote in message
> news:7F4792F3-8931-4E92-BEDA-0058D9917CFD@.microsoft.com...
>
>|||how does one:
enable the Allow Remote Connections option for the SQL2005 server
> instance?
I've set up ports and enabled tcp/ip, shared memory, pipes and do not see a
Allow Remote Connections option
I've shut off my firewall. I just installed sql server 2005 and am trying to
connect on the SAME MACHINE
"Landon Kelsey" wrote:
[vbcol=seagreen]
> I've serched high and low for this facility and cannot find it.
> I have enabled both client/server tcp/ip named pipes shared memory
> and still cannot connect.
> "Andrew J. Kelly" wrote:
>|||Try running through this quick tutorial to see if you missed anything:
http://msdn2.microsoft.com/en-us/library/ms345318(en-US,SQL.90).aspx
--
Rick Byham
MCDBA, MCSE, MCSA
Documentation Manager,
Microsoft, SQL Server Books Online
This posting is provided "as is" with
no warranties, and confers no rights.
"Landon Kelsey" <landonmkelsey@.hotmail.com> wrote in message
news:D98FEEC7-327F-4079-A971-B8A30A6D8FAE@.microsoft.com...[vbcol=seagreen]
> how does one:
> enable the Allow Remote Connections option for the SQL2005 server
> I've set up ports and enabled tcp/ip, shared memory, pipes and do not see
> a
> Allow Remote Connections option
> I've shut off my firewall. I just installed sql server 2005 and am trying
> to
> connect on the SAME MACHINE
>
> "Landon Kelsey" wrote:
>

Connection Broken - SQL 7.0 db migration to SQL 2000

Hi there,
I am trying to upgrade our sql server db from version 7.0
to version 2000. I was successly able to restore the sql
7.0 db into 2000 server. Everything seems to be working
fine except one important stored procedure.
When i execute this particular stored procedure,it works
fine for 2 attempts but crashes the server on the thrid
attempt. The error message i am getting is as follows:
[Microsoft][ODBC SQL Server Driver][DBNETLIB]
ConnectionCheckForData (CheckforData()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
Connection Broken
It will be great help if someone could shed some light on
this issue.
Thanks,
Savvy.
Hi
Rebuild all your indexes. I have seen this when the statistics get out of
date and you upgrade your DB.
Regards
Mike
"Savvy" wrote:

> Hi there,
> I am trying to upgrade our sql server db from version 7.0
> to version 2000. I was successly able to restore the sql
> 7.0 db into 2000 server. Everything seems to be working
> fine except one important stored procedure.
> When i execute this particular stored procedure,it works
> fine for 2 attempts but crashes the server on the thrid
> attempt. The error message i am getting is as follows:
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]
> ConnectionCheckForData (CheckforData()).
> Server: Msg 11, Level 16, State 1, Line 0
> General network error. Check your network documentation.
> Connection Broken
> It will be great help if someone could shed some light on
> this issue.
> Thanks,
> Savvy.
>

Connection Broken - SQL 7.0 db migration to SQL 2000

Hi there,
I am trying to upgrade our sql server db from version 7.0
to version 2000. I was successly able to restore the sql
7.0 db into 2000 server. Everything seems to be working
fine except one important stored procedure.
When i execute this particular stored procedure,it works
fine for 2 attempts but crashes the server on the thrid
attempt. The error message i am getting is as follows:
[Microsoft][ODBC SQL Server Driver][DBNETLIB]
ConnectionCheckForData (CheckforData()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
Connection Broken
It will be great help if someone could shed some light on
this issue.
Thanks,
Savvy.Hi
Rebuild all your indexes. I have seen this when the statistics get out of
date and you upgrade your DB.
Regards
Mike
"Savvy" wrote:
> Hi there,
> I am trying to upgrade our sql server db from version 7.0
> to version 2000. I was successly able to restore the sql
> 7.0 db into 2000 server. Everything seems to be working
> fine except one important stored procedure.
> When i execute this particular stored procedure,it works
> fine for 2 attempts but crashes the server on the thrid
> attempt. The error message i am getting is as follows:
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]
> ConnectionCheckForData (CheckforData()).
> Server: Msg 11, Level 16, State 1, Line 0
> General network error. Check your network documentation.
> Connection Broken
> It will be great help if someone could shed some light on
> this issue.
> Thanks,
> Savvy.
>

Connecting Visual Studio 2003 to SQL Server Express 2005 Edition

I was wondering if it is possible to connect the SQL Server 2005 Express Version to Visual Studio 2003.If its possible , how can it be done?Cos i seem to have an error if i do so.

You can check here for basic connectivity information:

http://msdn2.microsoft.com/en-us/library/ms345332.aspx

And make sure you check out the complete Express tutorial that Microsoft puts out for free:

http://msdn.microsoft.com/vstudio/express/sql/learning/default.aspx

Buck Woody

Connecting Visual Studio 2003 to SQL Server Express 2005 Edition

I was wondering if it is possible to connect the SQL Server 2005 Express Version to Visual Studio 2003.If its possible , how can it be done?Cos i seem to have an error if i do so.

You can check here for basic connectivity information:

http://msdn2.microsoft.com/en-us/library/ms345332.aspx

And make sure you check out the complete Express tutorial that Microsoft puts out for free:

http://msdn.microsoft.com/vstudio/express/sql/learning/default.aspx

Buck Woody

Connecting to sqlexpress from another machine.

I have developed an application in vs.net and have an sql express version on
one of my computers (Actually both computers).
How do I connect to this database from the other machine (workgroup, not
dedicated server)
When I try to connect through the Add Connection I get the message
'An error has occured while establishing a connection to the server. When
connecting to SQL Server 2005,
this failure may be caused by the fact under the default settings SQL Server
does not allow remote connections.
(Provider: SQL Network Interface, error: 26 -Error locating Server/Instance
Specified)'
reidarTHi
Can you connect using SQLCMD? It could be that you have not enable remote
connections with SqlSAC.exe! When you connect you should be able to specify
the machine name\Instance or the IP address\Instance in your connection
string. If you can connect using the IP address and not the hostname you may
need to add it to your hosts file.
John
"reidarT" wrote:
> I have developed an application in vs.net and have an sql express version on
> one of my computers (Actually both computers).
> How do I connect to this database from the other machine (workgroup, not
> dedicated server)
> When I try to connect through the Add Connection I get the message
> 'An error has occured while establishing a connection to the server. When
> connecting to SQL Server 2005,
> this failure may be caused by the fact under the default settings SQL Server
> does not allow remote connections.
> (Provider: SQL Network Interface, error: 26 -Error locating Server/Instance
> Specified)'
> reidarT
>
>|||reidarT wrote:
> I have developed an application in vs.net and have an sql express version on
> one of my computers (Actually both computers).
> How do I connect to this database from the other machine (workgroup, not
> dedicated server)
> When I try to connect through the Add Connection I get the message
> 'An error has occured while establishing a connection to the server. When
> connecting to SQL Server 2005,
> this failure may be caused by the fact under the default settings SQL Server
> does not allow remote connections.
> (Provider: SQL Network Interface, error: 26 -Error locating Server/Instance
> Specified)'
> reidarT
>
Use the Surface Area Configuration tool to enable remote connections...
Tracy McKibben
MCDBA
http://www.realsqlguy.com

Connecting to sqlexpress from another machine.

I have developed an application in vs.net and have an sql express version on
one of my computers (Actually both computers).
How do I connect to this database from the other machine (workgroup, not
dedicated server)
When I try to connect through the Add Connection I get the message
'An error has occured while establishing a connection to the server. When
connecting to SQL Server 2005,
this failure may be caused by the fact under the default settings SQL Server
does not allow remote connections.
(Provider: SQL Network Interface, error: 26 -Error locating Server/Instance
Specified)'
reidarTHi
Can you connect using SQLCMD? It could be that you have not enable remote
connections with SqlSAC.exe! When you connect you should be able to specify
the machine name\Instance or the IP address\Instance in your connection
string. If you can connect using the IP address and not the hostname you may
need to add it to your hosts file.
John
"reidarT" wrote:

> I have developed an application in vs.net and have an sql express version
on
> one of my computers (Actually both computers).
> How do I connect to this database from the other machine (workgroup, not
> dedicated server)
> When I try to connect through the Add Connection I get the message
> 'An error has occured while establishing a connection to the server. When
> connecting to SQL Server 2005,
> this failure may be caused by the fact under the default settings SQL Serv
er
> does not allow remote connections.
> (Provider: SQL Network Interface, error: 26 -Error locating Server/Instanc
e
> Specified)'
> reidarT
>
>|||reidarT wrote:
> I have developed an application in vs.net and have an sql express version
on
> one of my computers (Actually both computers).
> How do I connect to this database from the other machine (workgroup, not
> dedicated server)
> When I try to connect through the Add Connection I get the message
> 'An error has occured while establishing a connection to the server. When
> connecting to SQL Server 2005,
> this failure may be caused by the fact under the default settings SQL Serv
er
> does not allow remote connections.
> (Provider: SQL Network Interface, error: 26 -Error locating Server/Instanc
e
> Specified)'
> reidarT
>
Use the Surface Area Configuration tool to enable remote connections...
Tracy McKibben
MCDBA
http://www.realsqlguy.com

Connecting to SQL Server 2k5 Dev Edition

I recently removed my June CTP version of SS2k5 and installed the release developer version on a 2 proc server with Win Server 2003 SP1 (I'll call this machine Server), and suddenly I cannot connect to this box over our network. I have SS2k5 Dev Edition installed on my local machine (WinXP, and I'll call this machine Local), and was able to connect to the CTP version on the server with no problems. Now, not only can I not connect (or see the server through the network browse) to the Server from Local, nor can I connect or see my Local from the Server. I used the Surface Area Configuration tool to allow TCP/IP and Named Pipe connections (Local was set to local only connections, but was working fine to and from the CTP version of the Server), but to no avail.

Are there any other settings that I should look at? I'm working a bit in the dark here.

Thank you,

NoelHi Noel,

So I understand the problem you're experiencing, let me restate the problem. :)

On SERVER, which is Windows Server 2003 SP1, you have SQL 2005 Dev RTM.
On LOCAL, which is Windows XP SP2, you also have SQL 2005 Dev RTM.

When you say you "cannot see" SERVER from LOCAL or LOCAL from SERVER, what do you mean? Can you PING LOCAL from SERVER and vice versa by name? by IP?

Did you run the Surface Area Configurator on both machines and ensure Local + Remote access was enabled? After enabling TCP\IP and Named Pipes on LOCAL, did you stop and restart the service (this has to be done for the service to start listening on those protocols)?

jeff.|||Also, if your instance name is a named instance you'll need to start the SQL Browser service. If the Windows Firewall is enabled you'll need to add exceptions for sqlservr.exe and sqlbrowser.exe. To find the path to the correct SQL Server executable check out the "Path to executable" in the Windows Service Control Manager for the SQL Server service.

This blog for SQL Server Express is also relevant for Dev edition: http://blogs.msdn.com/sqlexpress/archive/2005/05/05/415084.aspx

Dan