Remotely Register SQL Server 2005 Express in Enterprise Manager

I have SQL Server 2005 Express installed on a windows server 2003 standard edition. I have configured the windows firewall to allow exceptions for sqlservr.exe and sqlbrowser.exe. I have enabled remote and local connections using tcp/ip & Named Pipes through the Sql Server Surface Area Connection utility. I am able to telnet into the server with: telnet <server ip> <1433>.

Here is the strange part: I am able to connect to the Sql Server remotely from a development machine via Sql Server Management Studio Express, but I am unable to connect to the Sql Server from the same development machine by registering it in Sql Server Enterprise Manager...Is it possible to register SQL Express through Enterprise Manager?

When registering the SQL Express DB in Enterprise Manager I tried both just the (IP Address) of the server and the (IP Address\SQLExpress) as the server/host but I am getting the following errors from enterprise manager:

Just the (IP Address) as the server/host:

Invalid Connection.

ConnectionOpen( Invalid Instance())

(IP Address\SQLEXPRESS) as the server/host:

Sql Server does not exist or access denied. ConnectOpen(Connect()).

Any idea why I can’t register/mount the instance remotely in Enterprise Manager

but I can in Sql Server Management Studio Express?

Thanks,

Greg

You can not use the Enterprise management tools with sql 2005, it is only for sql 2000 and below. The connection layer and management objects are different, but the SQL 2005 Management tools can read the lower version systems. Doing this you will notice that some functions can not be completed on the lower versions due to the differences in connections. For example you can not create a new maintenance plan in the sql 2005 tools to work on sql 2000, but you can edit it after it has been created using the old sql enterprise manager.

Remotely Register SQL Server 2005 Express in Enterprise Manager

I have SQL Server 2005 Express installed on a windows server 2003 standard edition. I have configured the windows firewall to allow exceptions for sqlservr.exe and sqlbrowser.exe. I have enabled remote and local connections using tcp/ip & Named Pipes through the Sql Server Surface Area Connection utility. I am able to telnet into the server with: telnet <server ip> <1433>.

Here is the strange part: I am able to connect to the Sql Server remotely from a development machine via Sql Server Management Studio Express, but I am unable to connect to the Sql Server from the same development machine by registering it in Sql Server Enterprise Manager...Is it possible to register SQL Express through Enterprise Manager?

When registering the SQL Express DB in Enterprise Manager I tried both just the (IP Address) of the server and the (IP Address\SQLExpress) as the server/host but I am getting the following errors from enterprise manager:

Just the (IP Address) as the server/host:

Invalid Connection.

ConnectionOpen( Invalid Instance())

(IP Address\SQLEXPRESS) as the server/host:

Sql Server does not exist or access denied. ConnectOpen(Connect()).

Any idea why I can’t register/mount the instance remotely in Enterprise Manager

but I can in Sql Server Management Studio Express?

Thanks,

Greg

You will not be able to register a sql2k5 on EM. EM uses sql2k dmo which can't be used to manage sql2k5.

You will have to use sql2k5 mgmt tool to manage sqlexpress/sql2k5 instances.|||

Hi OJ,

Thanks for the reply, I was afraid this was going to be the case. Well so here is the follow up to my question.

I am using Sql Server Management Studio Express (SSMSE)...so will I be able to connect/register a sql2k server to SSMSE?

Basically I want to export the data from my sql2K DB into my sql2k5 express DB so will I be able to do that with SSMSE or will I need the full version of Sql Server Management Studio?

Thanks,

Greg

|||I haven't explicitly looked at ssmse. However, I believe it uses smo. Thus, it's capable to connecting to sql2k and manage it.sql

Remote User Connection to SQL Server 7 Standard Edition

Is it possible to connect a remote user (in a wide area network) to a
database running on SQL Server 7 Standard Edition.
Do I need the Enterprise Edition to accomplish this?
Yes (to the first)
and
No (to the second)
Mike John
"guez" <guez@.discussions.microsoft.com> wrote in message
news:C4A2552E-74CA-4DDF-A1D1-4A1E05FB773C@.microsoft.com...
> Is it possible to connect a remote user (in a wide area network) to a
> database running on SQL Server 7 Standard Edition.
> Do I need the Enterprise Edition to accomplish this?

Remote User Connection to SQL Server 7 Standard Edition

Is it possible to connect a remote user (in a wide area network) to a
database running on SQL Server 7 Standard Edition.
Do I need the Enterprise Edition to accomplish this?Yes (to the first)
and
No (to the second)
Mike John
"guez" <guez@.discussions.microsoft.com> wrote in message
news:C4A2552E-74CA-4DDF-A1D1-4A1E05FB773C@.microsoft.com...
> Is it possible to connect a remote user (in a wide area network) to a
> database running on SQL Server 7 Standard Edition.
> Do I need the Enterprise Edition to accomplish this?

Remote User Connection to SQL Server 7 Standard Edition

Is it possible to connect a remote user (in a wide area network) to a
database running on SQL Server 7 Standard Edition.
Do I need the Enterprise Edition to accomplish this?Yes (to the first)
and
No (to the second)
Mike John
"guez" <guez@.discussions.microsoft.com> wrote in message
news:C4A2552E-74CA-4DDF-A1D1-4A1E05FB773C@.microsoft.com...
> Is it possible to connect a remote user (in a wide area network) to a
> database running on SQL Server 7 Standard Edition.
> Do I need the Enterprise Edition to accomplish this?sql

Remote SQL Access Through ISA (SBS 2003)

Hi All:
Our Software vendor needs to log on to SQL Server (we
have SBS 2003 Premium Edition)through ISA server. I have
followed microsoft direction and have opened port 1433.
He still cannot log on. He can log on through terminal
services but has no access to sql server. I have tried my
self and get the message that either the server does not
exsist or permission has been denied.
I can Ping the server sucessfully from remote site.
Please advice.
Thank you.
I have read articles # 300211 on microsoft web site in
knowledge base.
Many thanks for your time.
.Is your SQL Server a default or a named instance? If it's a default
instance then by default it listens on port 1433 but an admin could have
changed it to some other port. If it's a named instance then it will by
default use a dynamic port. You would need to check the Server Network
Utility on the server or read the latest SQL error log to see what port
your SQL Server is actually listening on and then open the appropriate port.
Also, if it's a named instance you will need to open UDP port 1434 OR
make your port static through the Server Network Utility AND specify the
port at the client (through an alias or by adding ,XXXX to the server name
in the connection string).
823938 How to use static and dynamic port allocation in SQL Server 2000
http://support.microsoft.com/?id=823938
You didn't mention the error you get, but most likely it's the one from:
328306 INF: Potential Causes of the "SQL Server Does Not Exist or Access
http://support.microsoft.com/?id=328306
Cindy Gross, MCDBA, MCSE
http://cindygross.tripod.com
This posting is provided "AS IS" with no warranties, and confers no rights.

Remote Setup on cluster node fail

Hi,

I've tried to install SQL Server 2005 September CTP as the first named instance on a Windows Server 2003 Enterprise Edition Cluster.

During the setup process a scheduled task is created on the second cluster node, but this task is not able to run.

I received this error message in the scheduled task log file:
0x80070005: Access is denied

The user account I'm using to install SQL Server is member of the administrator on all cluster nodes, it has also the permission to log on as a service and as a batch job. The user is also permitted to access the computer from the network.

Thanks in advance for the help!

Regards,
ClausThis might be caused by a known Windows bug. Task Scheduler service fails to launch setup on a remote node even if Task Scheduler is running. If someone is logged into remote node, they risk of hitting this Windows bug. Thefore log off any Terminal Server sessions from all remote nodes before you start setup. |||Hi Yim,

Yes! That's it - i logged of from the second cluster node and the installation completes successful!

Thanks a lot!

Remote logins for SQL 2000?

Hi all,
A company recently came in and setup SQL 2000 standard edition on our
Windows 2003 server. I've noticed that the password they setup for the SQL
user they created is not very secure. I am new to SQL, and I was wondering
if there is a way to remotely login to it? If not, I'll probably keep the
password the same, but if there is a way to log in remotely, I will
definately have to change it.
The user they created can be found under the Users section of the database
they setup and has the following access:
public
db_datareader
db_datawriterHi
Is it Window Authetntication or Mixed?

> Windows 2003 server. I've noticed that the password they setup for the
> SQL
> user they created is not very secure.
They created logins first to SQL Server and then added them to the database
"supersonic_oasis" <supersonicoasis@.discussions.microsoft.com> wrote in
message news:C9FE03CC-EF5A-414E-A103-B14F50EB13AB@.microsoft.com...
> Hi all,
> A company recently came in and setup SQL 2000 standard edition on our
> Windows 2003 server. I've noticed that the password they setup for the
> SQL
> user they created is not very secure. I am new to SQL, and I was
> wondering
> if there is a way to remotely login to it? If not, I'll probably keep the
> password the same, but if there is a way to log in remotely, I will
> definately have to change it.
> The user they created can be found under the Users section of the database
> they setup and has the following access:
> public
> db_datareader
> db_datawriter|||Yes you can remotely log into it, subject to various network security
issues of course.
J.
On Mon, 1 May 2006 04:22:01 -0700, supersonic_oasis
<supersonicoasis@.discussions.microsoft.com> wrote:

>Hi all,
>A company recently came in and setup SQL 2000 standard edition on our
>Windows 2003 server. I've noticed that the password they setup for the SQL
>user they created is not very secure. I am new to SQL, and I was wondering
>if there is a way to remotely login to it? If not, I'll probably keep the
>password the same, but if there is a way to log in remotely, I will
>definately have to change it.
>The user they created can be found under the Users section of the database
>they setup and has the following access:
>public
>db_datareader
>db_datawriter

Remote logins for SQL 2000?

Hi all,
A company recently came in and setup SQL 2000 standard edition on our
Windows 2003 server. I've noticed that the password they setup for the SQL
user they created is not very secure. I am new to SQL, and I was wondering
if there is a way to remotely login to it? If not, I'll probably keep the
password the same, but if there is a way to log in remotely, I will
definately have to change it.
The user they created can be found under the Users section of the database
they setup and has the following access:
public
db_datareader
db_datawriterHi
Is it Window Authetntication or Mixed?
> Windows 2003 server. I've noticed that the password they setup for the
> SQL
> user they created is not very secure.
They created logins first to SQL Server and then added them to the database
"supersonic_oasis" <supersonicoasis@.discussions.microsoft.com> wrote in
message news:C9FE03CC-EF5A-414E-A103-B14F50EB13AB@.microsoft.com...
> Hi all,
> A company recently came in and setup SQL 2000 standard edition on our
> Windows 2003 server. I've noticed that the password they setup for the
> SQL
> user they created is not very secure. I am new to SQL, and I was
> wondering
> if there is a way to remotely login to it? If not, I'll probably keep the
> password the same, but if there is a way to log in remotely, I will
> definately have to change it.
> The user they created can be found under the Users section of the database
> they setup and has the following access:
> public
> db_datareader
> db_datawriter|||Yes you can remotely log into it, subject to various network security
issues of course.
J.
On Mon, 1 May 2006 04:22:01 -0700, supersonic_oasis
<supersonicoasis@.discussions.microsoft.com> wrote:
>Hi all,
>A company recently came in and setup SQL 2000 standard edition on our
>Windows 2003 server. I've noticed that the password they setup for the SQL
>user they created is not very secure. I am new to SQL, and I was wondering
>if there is a way to remotely login to it? If not, I'll probably keep the
>password the same, but if there is a way to log in remotely, I will
>definately have to change it.
>The user they created can be found under the Users section of the database
>they setup and has the following access:
>public
>db_datareader
>db_datawriter

Remote login to MSDE 2000 (Desktop)

My question is, is it possible to connect to an SQL database using the MSDE 2000 SP3a edition over the internet? And if so, how do I set it up? Thank you in advance.::My question is, is it possible to connect to an SQL database using the MSDE 2000 SP3a
::edition over the internet?

Yes.

::And if so, how do I set it up?

You mean after making sure you can connect to the server from the internet, having a firewall in place etc.?

Not at all. There is nothing left to configure after this.

EVERY MSDE installation automatically accepts connections from the network, and guess what - the internet is just a network.

Remote Installation Create Response File

Hi,

Actaully i want to install SQL SERVER 2005 Enterprise edition in the silent mode and I was tyring to create a response file (setup.iss), but from the document provided i saw that SQL SERVER 2005 Enterprise edition doesnt create response file, and doesnt support setup.iss. So please provide me some solution where i can generate response file or some thing which is similar to that.

SQL 2005 now supports a ton of switches which will allow you to select all the GUI options from the command line. Check the docs on the DVD for all the options. Stick the finished command line in a batch file and use your favorite remote install tool to launch the batch file.|||

Here's the link in BOL for silent installs with a ton of examples:

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

Thanks,
Sam Lester (MSFT)

Remote Connections with SQL Developers Edition

Hi,

I want to allow someone to update the data in a database being developed in SQL Developers Edition. The idea is while I'm developing the database the person who's database it is can do the data entry. The data monkey lives no where near me so I cannot keep keep updating a local copy there...

I've tried to set up and connect but the server keeps refusing the connection. So question is... can SQL Developers Edition allow remote connections... and if so, which I hope it can, whats the way to go about setting it up.

Far as I can tell I'm ok in regards to specifying the location of the server, the SQL user account is set up and has access to the database.... can anyone help.

Yes dev edition supports remote connections, you need to go into the
surface area config tool and enable them however|||

Thank you Euan, thank you very much.

Can I also ask... can it work over a secured connection using TCP/IP and what would be involved in setting that up?

|||Whats your definition of secure? SQL Server supports SSL over the wire
is one way of securing it.|||Thats what I wanted to hear. Need to try find out to set it up so I may post again. Thanks.|||Try the security forum, they will be able to help.|||good idea thanks

Remote Connections using SQL Server 2005 Developers Enterprise Edition

I have a problem. I am using the developers version of SQL Server Enterprise edition.

I am trying to run a command in MS command prompt:

Aspnet_regsql -E -S localhost -ssadd -sstype p

After I execute this command, I receive a Name Pipe
error that under the default settings, SQL Server
doesn't allow remote connections. I took some steps
to try to resolve the problem:

1) I googled the interrnet to see if there was any one
else who ran into the same problem and if there was a
quick resolution.

2) I check SQL Server Books on line about SQL server
configuration manager and how to enable remote
connections using Name Pipes and TCP/IP.

3) I used C:\WINDOWS\system32\cliconfg.exe to enable
Name Pipes and TCPIP to be enable on the client.

4) I enabled SQl Server Browser to help me with my
problem

5) I stopped the Database engine, enable local and
remote connections using Name pipes and TCP/IP,then I
restarted the database engine along with SQl server
Agent.

6) I did check SQl Server error logs to see what port
it was listening on , but I thought that SQl Server
was suppose to listen on port 1433 by default, and
Name pipes /SQL/query.

7)I have check the error logs to see what port that SQL Server was listening to
and trying to use the port number in the client config utility. I am still getting the same error.

8) I tried to remove name pipes in the SQL Server Surface Manager and allow local and remote connections using only TCP/IP. I still get the same error. I did stop and restarted the Database Engine.

What steps have I not taken , and what should I do to correct this problem?

Hi,

have you refered below links?

http://blogs.msdn.com/sqlexpress/archive/2005/05/05/415084.aspx

http://support.microsoft.com/kb/914277/en-us

Hemantgiri S. Goswami

|||

Hi Hemantgiri,

Thank you for your reply.

I have reviewed the links that you recommended. I have completed most of the steps recommended. I am using a different firewall than Windows, and I will have to contact ZoneAlarm to receive more information about adding exceptions for SQL Server and SQL Server Browser. Usually, ZoneAlarm notify me to allow certain transactions to occur on my machine. I will ask the technical service people at ZoneAlarm why ZoneAlarm firewall was not informing me that it was blocking a remote connection to SQL Server from this machine. When I receive my requested information from ZoneAlarm and apply it to my firewall, I will let you know what happen next.

|||

Hi again,

I have taken the following steps to see if ZoneAlarm was presenting a problem. Please note that I have not heard from ZoneAlarm yet. I removed my wireless network card that I am using to conect to the internet. I disabled my ZoneAlarm and Windows firewall. I followed the steps in the article that was more focused on SQL Server Developer since I am not using SQL Express. I executed the command I mentioned earlier to see if I could connect to SQL Server remotely with out any firewall interference. I could not,and I received the same error. I did look at the other article that was more SQLExpress focused, but I am not sure how I would apply some commands in that article to SQL Server Developer. I have used the SQL Server Surface Configration to enable local and remote settings and using TCP/IP and Name Pipes. It shows that the radio buttons for both are selected, so I know that those choices are selected. As far as selecting a port, I am asking you what would be the SQLCMD command version for SQL Developer? The one for SQL Express is stated in the article, is there a similar one that I can use for SQL Developer? I tried to set the port using clientconfig.exe but that doesn't seem to work.

|||

Hi,

AFAIK their is no difference for the editions , you can perform the same steps.

Hemantgiri S. Goswami

|||

Hi everyone,

I am still looking into this situation. I do not know what to run the SQLCMD for SQL Developer. One article has it for SQL Express : SQLCMD -E -S YourServer\SQLEXPRESS,port #. My question is would I enter SQLCMD -E -S myserver\SQLDEVELOPER,port# or is there another way to state this?

|||

Hi everyone,

I have uninstalled the version of SQL Server 2005 and used an advanced version of SQL Express 2005. I have been successful in configuring remote connections and enabling Named Pipes and TCP/IP using this version. Even though I was not told by the previous version of SQL server 2005, I think that I did not correctly add myself to the Admin group to have the rights to change from local to local /remote connections and enable Named Pipes and TCP/IP. I will test my theory when I install my Standard edition of SQL Server 2005 during May or June.

I would like to thank everyone who replied to my post or who thought hard on a solution to my problem, but have not replied at this time.

Remote Connections using SQL Server 2005 Developers Enterprise Edition

I have a problem. I am using the developers version of SQL Server Enterprise edition.

I am trying to run a command in MS command prompt:

Aspnet_regsql -E -S localhost -ssadd -sstype p

After I execute this command, I receive a Name Pipe
error that under the default settings, SQL Server
doesn't allow remote connections. I took some steps
to try to resolve the problem:

1) I googled the interrnet to see if there was any one
else who ran into the same problem and if there was a
quick resolution.

2) I check SQL Server Books on line about SQL server
configuration manager and how to enable remote
connections using Name Pipes and TCP/IP.

3) I used C:\WINDOWS\system32\cliconfg.exe to enable
Name Pipes and TCPIP to be enable on the client.

4) I enabled SQl Server Browser to help me with my
problem

5) I stopped the Database engine, enable local and
remote connections using Name pipes and TCP/IP,then I
restarted the database engine along with SQl server
Agent.

6) I did check SQl Server error logs to see what port
it was listening on , but I thought that SQl Server
was suppose to listen on port 1433 by default, and
Name pipes /SQL/query.

7)I have check the error logs to see what port that SQL Server was listening to
and trying to use the port number in the client config utility. I am still getting the same error.

8) I tried to remove name pipes in the SQL Server Surface Manager and allow local and remote connections using only TCP/IP. I still get the same error. I did stop and restarted the Database Engine.

What steps have I not taken , and what should I do to correct this problem?

Hi,

have you refered below links?

http://blogs.msdn.com/sqlexpress/archive/2005/05/05/415084.aspx

http://support.microsoft.com/kb/914277/en-us

Hemantgiri S. Goswami

|||

Hi Hemantgiri,

Thank you for your reply.

I have reviewed the links that you recommended. I have completed most of the steps recommended. I am using a different firewall than Windows, and I will have to contact ZoneAlarm to receive more information about adding exceptions for SQL Server and SQL Server Browser. Usually, ZoneAlarm notify me to allow certain transactions to occur on my machine. I will ask the technical service people at ZoneAlarm why ZoneAlarm firewall was not informing me that it was blocking a remote connection to SQL Server from this machine. When I receive my requested information from ZoneAlarm and apply it to my firewall, I will let you know what happen next.

|||

Hi again,

I have taken the following steps to see if ZoneAlarm was presenting a problem. Please note that I have not heard from ZoneAlarm yet. I removed my wireless network card that I am using to conect to the internet. I disabled my ZoneAlarm and Windows firewall. I followed the steps in the article that was more focused on SQL Server Developer since I am not using SQL Express. I executed the command I mentioned earlier to see if I could connect to SQL Server remotely with out any firewall interference. I could not,and I received the same error. I did look at the other article that was more SQLExpress focused, but I am not sure how I would apply some commands in that article to SQL Server Developer. I have used the SQL Server Surface Configration to enable local and remote settings and using TCP/IP and Name Pipes. It shows that the radio buttons for both are selected, so I know that those choices are selected. As far as selecting a port, I am asking you what would be the SQLCMD command version for SQL Developer? The one for SQL Express is stated in the article, is there a similar one that I can use for SQL Developer? I tried to set the port using clientconfig.exe but that doesn't seem to work.

|||

Hi,

AFAIK their is no difference for the editions , you can perform the same steps.

Hemantgiri S. Goswami

|||

Hi everyone,

I am still looking into this situation. I do not know what to run the SQLCMD for SQL Developer. One article has it for SQL Express : SQLCMD -E -S YourServer\SQLEXPRESS,port #. My question is would I enter SQLCMD -E -S myserver\SQLDEVELOPER,port# or is there another way to state this?

|||

Hi everyone,

I have uninstalled the version of SQL Server 2005 and used an advanced version of SQL Express 2005. I have been successful in configuring remote connections and enabling Named Pipes and TCP/IP using this version. Even though I was not told by the previous version of SQL server 2005, I think that I did not correctly add myself to the Admin group to have the rights to change from local to local /remote connections and enable Named Pipes and TCP/IP. I will test my theory when I install my Standard edition of SQL Server 2005 during May or June.

I would like to thank everyone who replied to my post or who thought hard on a solution to my problem, but have not replied at this time.

Remote Connection with SQL Server 2005 Developer Edition

Can I do a Remote Connection with SQL Sever 2005 Developer Editio?

Yes. You have to enable the remoteconnections first:

http://www.sqlserver2005.de/sharedFiles/remoteconnection.jpg

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

Remote Connection problems, I've read many a thread on this and nothing has worked!

Hi, I am trying to enable remote access on a SQL Server 2005 standard edition instance. I have enabled it in the properties using the Management studio and have enabled it under Sql Server Surface Area Configuration under "Database engine".

But it didn't work. I know for a fact that my connection string is correct (I tested it on the actual machine)

So I checked everything again and I noticed in the Sql Server Surface Area under "Analysis Services" there is another "remote connection" checkbox to be enabled, however it won't let me enable it there because it says the "Sql Browser" is not started. I checked and the Sql Browser is started.

I'm thinking maybe the problem there is that I have an instance of SQL 2000 running and perhaps it is the sql browser for that (I can remotely connect ot my SQL 2000 instance).

I checked under Computer management -> services and their is no SQL Browser for the instance of SQL 2005. Not even a thing to enable. Just the Default instance SQL Browser, which is for my SQL 2000 instance. Am I missing something here?

Also there is no SQL Browser to enable in the management or Surface Area Configuration programs.

I have also tried to connect using the default port number (1433) and the IP (to bypass the need for the SQL Browser). It apparently finds my Server 2000 instance because it doesn't accept my user name and password and connot find the specific database (note: I verified the username and pswd are correct by testing the values on the SQL machine). How do I find what port number a specific instance of SQL Server is running on?

Hi,

the fact that you are using the default instance of SQL Server 2000 on your computer and that you can connect to the SQL Server 2k with the default settings (1433) indicates that SQL Server 2l5 is installed on another port than 1433, because ports can′t be shared. So try to see on which port you installed SQL Server 2k and on therefore on which port it is listening. Then specify the port within your connection string with the following syntax:

MachineName\instanceName,Portnumber

HTH; Jens Suessmeyer.

http://www.sqlserver2005.de
|||

I've tried figuring out what port the SQL 2005 is running on by running a port scan, but nothing really jumped out at me other than the 1433, which the SQL 2000 is running on.

What is a good way to find out what port the SQL 2005 is running on?

|||

Hi,

you can have a look at:

http://support.microsoft.com/default.aspx?scid=kb;en-us;823938

The port which SQL Server is listening to can be retrieved via looking in the eventlog or using the statement xp_readerrorlog which shows up something like "SQL Server listening on xxx.xxx.xxx.xxx:PortNumber"

HTH, Jens Suessmeyer.

http//www.sqlserver2005.de

remote connection of the sql reports in express edition

Hello Dear Friends

I work for a small organization and on my reference my team downloaded the Sql express edition of web developer and Sql server

WE have worked on two products

And now i understand that "Report data sources must be SQL Server relational databases that run locally in SQL Server Express" !!!!!!!!

We are able to connect sqlserver database

The work on products is almost complete and at this point cannot revert back to any other reporting services.

DO I HAVE HOPE...is there any way to connect to ssrs remotely ? Please help

Our Client has branches at two locations so the database will be on the server and he would want to acess reports at both places

Please somebody help me as to what should i do?

Sara

Can somebody help me please

Sara

|||

Hello friends

Does anybody have an answer?

Sara