Can not find report server on the machine

I installed SQL Server 2005 which include report server but got this error: no report servers were found on this server when trying to configure report server. Am I missing something?

Thanks

Moving to SSRS forum.|||You need to check to see if IIS is up and running. What version is the OS? HTH|||

Go to Services and make sure SQL Server Reporting Services (MSSQLSERVER) service is started.

Shyam

Can not create Maintenance Plan - getting error message

I just setup two new SQL 2005 Stnd x64bit servers for a customer. The
original two servers running the same SQL version have been running
fine for 3 weeks now. The mian production database is attached and SQL
seems to be working fine. When I try to create a new Maintenance Plan
or use the Maint Plan wizard, I get an error message.
The error message:
TITLE: Microsoft SQL Server Management Studio
--
The action you attempted to perform on a remote instance of SQL Server
has failed because the action requires a SQL Server component that is
not installed on the remote computer. To proceed, install SQL Server
2005 Management Tools on the remote computer, and then try again. For
more information, see "How to: Install SQL Server 2005 (Setup)" in SQL
Server 2005 Books Online, or find the article on MSDN at
http://go.microsoft.com/fwlink/?LinkID=57083 . (ObjectExplorer)
For help, click: http://go.microsoft.com/fwlink/?LinkID=57083
----
I did run SCW on the new servers just like I did on the two original
servers.
Any thoughts? ThanksHi,
I get the exact same error - have you found a solution for your problem
yet?
My setup is a 2 node cluster with SQL 2005 SP1
Regards
Jon skrev:
> I just setup two new SQL 2005 Stnd x64bit servers for a customer. The
> original two servers running the same SQL version have been running
> fine for 3 weeks now. The mian production database is attached and SQL
> seems to be working fine. When I try to create a new Maintenance Plan
> or use the Maint Plan wizard, I get an error message.
> The error message:
> TITLE: Microsoft SQL Server Management Studio
> --
> The action you attempted to perform on a remote instance of SQL Server
> has failed because the action requires a SQL Server component that is
> not installed on the remote computer. To proceed, install SQL Server
> 2005 Management Tools on the remote computer, and then try again. For
> more information, see "How to: Install SQL Server 2005 (Setup)" in SQL
> Server 2005 Books Online, or find the article on MSDN at
> http://go.microsoft.com/fwlink/?LinkID=57083 . (ObjectExplorer)
> For help, click: http://go.microsoft.com/fwlink/?LinkID=57083
> ----
> I did run SCW on the new servers just like I did on the two original
> servers.
> Any thoughts? Thanks

Can not create Maintenance Plan - getting error message

I just setup two new SQL 2005 Stnd x64bit servers for a customer. The
original two servers running the same SQL version have been running
fine for 3 weeks now. The mian production database is attached and SQL
seems to be working fine. When I try to create a new Maintenance Plan
or use the Maint Plan wizard, I get an error message.
The error message:
TITLE: Microsoft SQL Server Management Studio
--
The action you attempted to perform on a remote instance of SQL Server
has failed because the action requires a SQL Server component that is
not installed on the remote computer. To proceed, install SQL Server
2005 Management Tools on the remote computer, and then try again. For
more information, see "How to: Install SQL Server 2005 (Setup)" in SQL
Server 2005 Books Online, or find the article on MSDN at
http://go.microsoft.com/fwlink/?LinkID=57083 . (ObjectExplorer)
For help, click: http://go.microsoft.com/fwlink/?LinkID=57083
----
--
I did run SCW on the new servers just like I did on the two original
servers.
Any thoughts? ThanksHi,
I get the exact same error - have you found a solution for your problem
yet?
My setup is a 2 node cluster with SQL 2005 SP1
Regards
Jon skrev:

> I just setup two new SQL 2005 Stnd x64bit servers for a customer. The
> original two servers running the same SQL version have been running
> fine for 3 weeks now. The mian production database is attached and SQL
> seems to be working fine. When I try to create a new Maintenance Plan
> or use the Maint Plan wizard, I get an error message.
> The error message:
> TITLE: Microsoft SQL Server Management Studio
> --
> The action you attempted to perform on a remote instance of SQL Server
> has failed because the action requires a SQL Server component that is
> not installed on the remote computer. To proceed, install SQL Server
> 2005 Management Tools on the remote computer, and then try again. For
> more information, see "How to: Install SQL Server 2005 (Setup)" in SQL
> Server 2005 Books Online, or find the article on MSDN at
> http://go.microsoft.com/fwlink/?LinkID=57083 . (ObjectExplorer)
> For help, click: http://go.microsoft.com/fwlink/?LinkID=57083
> ----
--
> I did run SCW on the new servers just like I did on the two original
> servers.
> Any thoughts? Thanks

Can not create maintenance plan

I have had two SQL 2005 Stnd x64bit servers running without any problems for several weeks now. I just setup two new ones last night. One the two new ones, I get an error message when I try to create a Maintenance Plan. I also get an error when I try to create a plan using the Wizard.

The error message is:
TITLE: Microsoft SQL Server Management Studio

The action you attempted to perform on a remote instance of SQL Server has failed
because the action requires a SQL Server component that is not installed on the
remote computer. To proceed, install SQL Server 2005 Management Tools on the remote
computer, and then try again. For more information, see "How to: Install SQL Server
2005 (Setup)" in SQL Server 2005 Books Online, or find the article on MSDN at
http://go.microsoft.com/fwlink/?LinkID=57083 . (ObjectExplorer)

For help, click: http://go.microsoft.com/fwlink/?LinkID=57083

Note: SQL Agent is running. So far, everything else seems to be working fine.

Any ideas?

Thanks in advance.

jtwDitto -- same problem, same server type. I observed that it was accessible prior to SP1 but not afterwards. Post-SP1 hotfixes did not solve problem either.|||

Can you make sure you have installed Integrated Service as it should be installed in order to create maintenance plans from the SQL Manager.

Thanks

|||

Hi,

I have the same issue - post sp1 on 2005 64bit. I was under the impression that sp1 removed the need for SSIS when creating maintenance plans.

I just go round in circles trying to reinstall the management tools - but it wont let me as the install cd is now an old version (RTM) and you cant slipstream SP1... do i have to install SSIS?

thanks

Luke

|||

Yes you do need to have SSIS installed to get all the right components to Maintance plans working. This is one of the fixes targeted for SP2 but for right now you need to install SSIS.

Michelle

Can not create maintenance plan

I have had two SQL 2005 Stnd x64bit servers running without any problems for several weeks now. I just setup two new ones last night. One the two new ones, I get an error message when I try to create a Maintenance Plan. I also get an error when I try to create a plan using the Wizard.

The error message is:
TITLE: Microsoft SQL Server Management Studio

The action you attempted to perform on a remote instance of SQL Server has failed
because the action requires a SQL Server component that is not installed on the
remote computer. To proceed, install SQL Server 2005 Management Tools on the remote
computer, and then try again. For more information, see "How to: Install SQL Server
2005 (Setup)" in SQL Server 2005 Books Online, or find the article on MSDN at
http://go.microsoft.com/fwlink/?LinkID=57083 . (ObjectExplorer)

For help, click: http://go.microsoft.com/fwlink/?LinkID=57083

Note: SQL Agent is running. So far, everything else seems to be working fine.

Any ideas?

Thanks in advance.

jtwDitto -- same problem, same server type. I observed that it was accessible prior to SP1 but not afterwards. Post-SP1 hotfixes did not solve problem either.|||

Can you make sure you have installed Integrated Service as it should be installed in order to create maintenance plans from the SQL Manager.

Thanks

|||

Hi,

I have the same issue - post sp1 on 2005 64bit. I was under the impression that sp1 removed the need for SSIS when creating maintenance plans.

I just go round in circles trying to reinstall the management tools - but it wont let me as the install cd is now an old version (RTM) and you cant slipstream SP1... do i have to install SSIS?

thanks

Luke

|||

Yes you do need to have SSIS installed to get all the right components to Maintance plans working. This is one of the fixes targeted for SP2 but for right now you need to install SSIS.

Michelle

Can not create maintenance plan

I have had two SQL 2005 Stnd x64bit servers running without any problems for several weeks now. I just setup two new ones last night. One the two new ones, I get an error message when I try to create a Maintenance Plan. I also get an error when I try to create a plan using the Wizard.

The error message is:
TITLE: Microsoft SQL Server Management Studio

The action you attempted to perform on a remote instance of SQL Server has failed
because the action requires a SQL Server component that is not installed on the
remote computer. To proceed, install SQL Server 2005 Management Tools on the remote
computer, and then try again. For more information, see "How to: Install SQL Server
2005 (Setup)" in SQL Server 2005 Books Online, or find the article on MSDN at
http://go.microsoft.com/fwlink/?LinkID=57083 . (ObjectExplorer)

For help, click: http://go.microsoft.com/fwlink/?LinkID=57083

Note: SQL Agent is running. So far, everything else seems to be working fine.

Any ideas?

Thanks in advance.

jtwDitto -- same problem, same server type. I observed that it was accessible prior to SP1 but not afterwards. Post-SP1 hotfixes did not solve problem either.|||

Can you make sure you have installed Integrated Service as it should be installed in order to create maintenance plans from the SQL Manager.

Thanks

|||

Hi,

I have the same issue - post sp1 on 2005 64bit. I was under the impression that sp1 removed the need for SSIS when creating maintenance plans.

I just go round in circles trying to reinstall the management tools - but it wont let me as the install cd is now an old version (RTM) and you cant slipstream SP1... do i have to install SSIS?

thanks

Luke

|||

Yes you do need to have SSIS installed to get all the right components to Maintance plans working. This is one of the fixes targeted for SP2 but for right now you need to install SSIS.

Michelle

sql

Can not create maintenance plan

I have had two SQL 2005 Stnd x64bit servers running without any problems for several weeks now. I just setup two new ones last night. One the two new ones, I get an error message when I try to create a Maintenance Plan. I also get an error when I try to create a plan using the Wizard.

The error message is:
TITLE: Microsoft SQL Server Management Studio

The action you attempted to perform on a remote instance of SQL Server has failed
because the action requires a SQL Server component that is not installed on the
remote computer. To proceed, install SQL Server 2005 Management Tools on the remote
computer, and then try again. For more information, see "How to: Install SQL Server
2005 (Setup)" in SQL Server 2005 Books Online, or find the article on MSDN at
http://go.microsoft.com/fwlink/?LinkID=57083 . (ObjectExplorer)

For help, click: http://go.microsoft.com/fwlink/?LinkID=57083

Note: SQL Agent is running. So far, everything else seems to be working fine.

Any ideas?

Thanks in advance.

jtwDitto -- same problem, same server type. I observed that it was accessible prior to SP1 but not afterwards. Post-SP1 hotfixes did not solve problem either.|||

Can you make sure you have installed Integrated Service as it should be installed in order to create maintenance plans from the SQL Manager.

Thanks

|||

Hi,

I have the same issue - post sp1 on 2005 64bit. I was under the impression that sp1 removed the need for SSIS when creating maintenance plans.

I just go round in circles trying to reinstall the management tools - but it wont let me as the install cd is now an old version (RTM) and you cant slipstream SP1... do i have to install SSIS?

thanks

Luke

|||

Yes you do need to have SSIS installed to get all the right components to Maintance plans working. This is one of the fixes targeted for SP2 but for right now you need to install SSIS.

Michelle

can not connect with system account

we have two non-sql servers (a & b) that connect to a third sql server with
their system account (servername$). We have permissioned the system accounts
in SQL. However, server a is able to connect with it's system account and b
is not.
When I schedule a batch file to connect to the sql server using osql, server
b 's connection errors out with the error: Login failed for user 'NT
AUTHORITY\ANONYMOUS LOGON'.
DBA72 wrote:
> we have two non-sql servers (a & b) that connect to a third sql
> server with their system account (servername$). We have permissioned
> the system accounts in SQL. However, server a is able to connect with
> it's system account and b is not.
> When I schedule a batch file to connect to the sql server using osql,
> server b 's connection errors out with the error: Login failed for
> user 'NT AUTHORITY\ANONYMOUS LOGON'.
Why not create an account for SQL Server and use it for the service.
David Gugick
Imceda Software
www.imceda.com
|||This is for an SMS setup and apparently, under advanced security settings,
the SMS service on other servers is supposed to run under the system account.
"David Gugick" wrote:

> DBA72 wrote:
> Why not create an account for SQL Server and use it for the service.
> --
> David Gugick
> Imceda Software
> www.imceda.com
>
|||Are these two (three) servers in different domains? Are any of them running
on NT 4 servers? The fact that you received anonymous logon errors says the
SQL Server domain controller doesn't know anything about the system account
that this server is passing to the SQL Server.
Another possibility is that server b's system account password has not been
able to successfully synchronize with its domain controller.
Lastly, the NT AUTHORITY accounts are not; they are Windows AD Groups. So,
either NT AUTHORITY\SYSTEM or NT AUTHORITY\ANONYMOUS LOGON can be granted
access to your SQL Server. However, they include several systems and/or
unkown users. Give whatever access very limited rights with your SQL Server
and user databases. Luckily, these accounts are restricted to the domain
that hosts them; so, if you are in a secured WAN\LAN, it will be less of a
threat.
Sincerely,
Anthony Thomas

"DBA72" <DBA72@.discussions.microsoft.com> wrote in message
news:BF1203C3-3219-484A-99BC-661B4B8C6A72@.microsoft.com...
This is for an SMS setup and apparently, under advanced security settings,
the SMS service on other servers is supposed to run under the system
account.
"David Gugick" wrote:

> DBA72 wrote:
> Why not create an account for SQL Server and use it for the service.
> --
> David Gugick
> Imceda Software
> www.imceda.com
>

can not connect with system account

we have two non-sql servers (a & b) that connect to a third sql server with
their system account (servername$). We have permissioned the system accounts
in SQL. However, server a is able to connect with it's system account and b
is not.
When I schedule a batch file to connect to the sql server using osql, server
b 's connection errors out with the error: Login failed for user 'NT
AUTHORITY\ANONYMOUS LOGON'.DBA72 wrote:
> we have two non-sql servers (a & b) that connect to a third sql
> server with their system account (servername$). We have permissioned
> the system accounts in SQL. However, server a is able to connect with
> it's system account and b is not.
> When I schedule a batch file to connect to the sql server using osql,
> server b 's connection errors out with the error: Login failed for
> user 'NT AUTHORITY\ANONYMOUS LOGON'.
Why not create an account for SQL Server and use it for the service.
David Gugick
Imceda Software
www.imceda.com|||This is for an SMS setup and apparently, under advanced security settings,
the SMS service on other servers is supposed to run under the system account
.
"David Gugick" wrote:

> DBA72 wrote:
> Why not create an account for SQL Server and use it for the service.
> --
> David Gugick
> Imceda Software
> www.imceda.com
>|||Are these two (three) servers in different domains? Are any of them running
on NT 4 servers? The fact that you received anonymous logon errors says the
SQL Server domain controller doesn't know anything about the system account
that this server is passing to the SQL Server.
Another possibility is that server b's system account password has not been
able to successfully synchronize with its domain controller.
Lastly, the NT AUTHORITY accounts are not; they are Windows AD Groups. So,
either NT AUTHORITY\SYSTEM or NT AUTHORITY\ANONYMOUS LOGON can be granted
access to your SQL Server. However, they include several systems and/or
unkown users. Give whatever access very limited rights with your SQL Server
and user databases. Luckily, these accounts are restricted to the domain
that hosts them; so, if you are in a secured WAN\LAN, it will be less of a
threat.
Sincerely,
Anthony Thomas
"DBA72" <DBA72@.discussions.microsoft.com> wrote in message
news:BF1203C3-3219-484A-99BC-661B4B8C6A72@.microsoft.com...
This is for an SMS setup and apparently, under advanced security settings,
the SMS service on other servers is supposed to run under the system
account.
"David Gugick" wrote:

> DBA72 wrote:
> Why not create an account for SQL Server and use it for the service.
> --
> David Gugick
> Imceda Software
> www.imceda.com
>

can not connect with system account

we have two non-sql servers (a & b) that connect to a third sql server with
their system account (servername$). We have permissioned the system accounts
in SQL. However, server a is able to connect with it's system account and b
is not.
When I schedule a batch file to connect to the sql server using osql, server
b 's connection errors out with the error: Login failed for user 'NT
AUTHORITY\ANONYMOUS LOGON'.DBA72 wrote:
> we have two non-sql servers (a & b) that connect to a third sql
> server with their system account (servername$). We have permissioned
> the system accounts in SQL. However, server a is able to connect with
> it's system account and b is not.
> When I schedule a batch file to connect to the sql server using osql,
> server b 's connection errors out with the error: Login failed for
> user 'NT AUTHORITY\ANONYMOUS LOGON'.
Why not create an account for SQL Server and use it for the service.
--
David Gugick
Imceda Software
www.imceda.com|||This is for an SMS setup and apparently, under advanced security settings,
the SMS service on other servers is supposed to run under the system account.
"David Gugick" wrote:
> DBA72 wrote:
> > we have two non-sql servers (a & b) that connect to a third sql
> > server with their system account (servername$). We have permissioned
> > the system accounts in SQL. However, server a is able to connect with
> > it's system account and b is not.
> > When I schedule a batch file to connect to the sql server using osql,
> > server b 's connection errors out with the error: Login failed for
> > user 'NT AUTHORITY\ANONYMOUS LOGON'.
> Why not create an account for SQL Server and use it for the service.
> --
> David Gugick
> Imceda Software
> www.imceda.com
>|||Are these two (three) servers in different domains? Are any of them running
on NT 4 servers? The fact that you received anonymous logon errors says the
SQL Server domain controller doesn't know anything about the system account
that this server is passing to the SQL Server.
Another possibility is that server b's system account password has not been
able to successfully synchronize with its domain controller.
Lastly, the NT AUTHORITY accounts are not; they are Windows AD Groups. So,
either NT AUTHORITY\SYSTEM or NT AUTHORITY\ANONYMOUS LOGON can be granted
access to your SQL Server. However, they include several systems and/or
unkown users. Give whatever access very limited rights with your SQL Server
and user databases. Luckily, these accounts are restricted to the domain
that hosts them; so, if you are in a secured WAN\LAN, it will be less of a
threat.
Sincerely,
Anthony Thomas
"DBA72" <DBA72@.discussions.microsoft.com> wrote in message
news:BF1203C3-3219-484A-99BC-661B4B8C6A72@.microsoft.com...
This is for an SMS setup and apparently, under advanced security settings,
the SMS service on other servers is supposed to run under the system
account.
"David Gugick" wrote:
> DBA72 wrote:
> > we have two non-sql servers (a & b) that connect to a third sql
> > server with their system account (servername$). We have permissioned
> > the system accounts in SQL. However, server a is able to connect with
> > it's system account and b is not.
> > When I schedule a batch file to connect to the sql server using osql,
> > server b 's connection errors out with the error: Login failed for
> > user 'NT AUTHORITY\ANONYMOUS LOGON'.
> Why not create an account for SQL Server and use it for the service.
> --
> David Gugick
> Imceda Software
> www.imceda.com
>

Can not connect to SQL Server from DMZ

We just moved to a new office. After setting up the servers, we found
that the apllication (including SQL Query Analyzer) in DMZ can not
access SQL server that is behind the firewall. We can ping the SQL
server from the server in DMZ and we also checked and confirmed port
1433 is open from the firewall. Could anyone help me out?
Thanks,Run the following test:
ISQL -Stcp:sqlnamehere -Uuserid -Ppassword -Q"select @.@.version"
Post the Error message.
Winsock Error messages should be returned if it fails.
Example:
11001 == Host Not Found
10060 == Connection Timeout
10061 == Connection Refused
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.

Can multiple Reporting Services use one SQL Server?

I'm working with a team that's trying to get a new set of development servers working and have run into all sorts of issues, mostly w/ Team Foundation Server and RS, but it has caused to us to ask a number of questions about the use of RS.

All our servers are virtual servers, running W2003. We have:

+ one SQL 2005 server installed w/ SSIS, SSAS, and just the RS databases.

+ one Web server (IIS6) hosting multiple websites. I installed the RS server components on this server as well.

+ [attempting to get working] on Team Foundation Server (TFS) using the previously mentioned SQL Server as its data tier; Report Server installed on this box too, by TFS.

Getting the SQL and Web server boxes installed and running was a snap, no problems there. TFS, on the other hand, has been a nightmare. So here's my question, based on various incongruent feedback from tech support...

Can there be multiple applications (like mulitple different web servers (not a web farm, but say 2 distinct and different web server boxes, and something like a TFS server) all use one SQL Server's Reporting Server databases on the backend?

It seems as if we're being told that either it can't be done or perhaps we need to use SQL Server Enterprise edition... which would blow out our expenses considerably.

Can anyone shed light on this? Thanks in advance.

If you have 2 RS instances (web servers) connecting to the same RS database, it is a web farm scenario and requires enterprise edition.

On the other hand, you can have 2 RS instances (web servers) each connecting to its own database. If the RS instance and its database is on different servers, you will need enterprise or standard edition. If they are on the same server, you can use any edition.

|||

"each connecting to its own database"... OK, I might need some more help on that. So, I run SQL Server setup on WebServer1. OK, that's fine so far. Does that create the ReportServer and ReportServerTempDB databases on my single SQL Server box?

Now, I run the SQL Server setup disc on WebServer2, do I need to tell it to use different database names at some point?

Sorry for the confusion, just trying to get clarity around all this. I have two separate web servers and one sql server, 3 all told (actually 1 physical box, 3 virtual servers, but that shouldn't matter should it?). WebServer1 and WebServer2 are running different websites altogether. I want each web server to be able to use Reporting Services technology as needed and I want to only have one Sql Server box, preferably Std Edition. I guess that's what I'm trying to find out if it's feasible.

Thanks again.

|||

Virtual server makes no different in the argument.

Do you need the 2 web sites to share content? (i.e. you upload a report to website1, and it shows up on website2) If so the 2 websites need to point to the same RS databases on your SQL machine, and it's a web farm scenario.

If the websites can be independent, then you can use standard edition. You install RS on webserver1, using the "file-only" install option. Post-install you use the configuration tool and create RS databases for webserver1. You do the same for webserver2, but the database will be different. There will be a total of 4 databases on the SQL machine, 2 for webserver1, and 2 for webserver2.

Can I use osql to known the database install on a server via guest ?

Can I use osql to known the database install on a server via 'guest'
account ?

I had over 300 servers with sql server all around France (different
version : 6.5, 7 and 8)
I need to check all database on each servers from my place.
Of course, also it would have been to easy, I don't have all 'sa'
password...

Is that possible to use the 'guest' account to execute a query like
this via osql :

Extract.sql
exec sp_helpdb

Extract.cmd
for /f "usebackq tokens=1 delims=\n" %%i IN (ListServer.txt) DO
osql
-S%%i -Uguest -P -dmaster -i"C:\Extraction\Extract.sql"
-o"C:\Extraction\%%i.rpt"

Could I query 'master' with the 'guest' account ?
Or any other ideas how to do this by an other way ?

ThanksFlorimond (florimond@.gmail.com) writes:
> Can I use osql to known the database install on a server via 'guest'
> account ?
> I had over 300 servers with sql server all around France (different
> version : 6.5, 7 and 8)
> I need to check all database on each servers from my place.
> Of course, also it would have been to easy, I don't have all 'sa'
> password...
> Is that possible to use the 'guest' account to execute a query like
> this via osql :

"guest" is not a login, it's only a database user. To connect to SQL
Server you must either have a valid username/password for SQL
authentication, or your Windows login must have been granted access
to the server.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp

Can I run Report Engine and Report Manager in different servers?

The Subject is the whole question: Can I run Report Engine and Report Manager
in different servers?
This is because of my current network infra-strucutre.. I know that
ReportServer is a Web-Service and Report Manager is a Web Application that
consumes this Web-Service, so I would like to know how can I configure this
App to run in another server and access the remote web service.
Thx,
Rafa®AFAIK, the only splitting of the features can be done by dividing the
database and the ReportServer (Web and Service). Nethertheless, if you could
divide them you would need two licences of SQL Server either. So building of
two ReportServers which can be connected to only one Reporting Database is
possible on by design. See SQL Server Reporting Secifications for more
Details.
HTH, Jens Süßmeyer.
--
http://www.sqlserver2005.de
--
"Rafa®" <Rafa@.discussions.microsoft.com> schrieb im Newsbeitrag
news:1DC7543E-F51B-4F53-BC0E-8D323B635967@.microsoft.com...
> The Subject is the whole question: Can I run Report Engine and Report
> Manager
> in different servers?
> This is because of my current network infra-strucutre.. I know that
> ReportServer is a Web-Service and Report Manager is a Web Application that
> consumes this Web-Service, so I would like to know how can I configure
> this
> App to run in another server and access the remote web service.
> Thx,
> Rafa®

Can I replace my BCP with log shipping?

I have 2 SQL servers at a remote site and currently we FTP BCP data to our London site that is then BCP into other SQL databases.

I am wanting to simplify this and get rid of all the batch files we have and do the following...

Log ship from the remote site to London over the internet. The log shipping server can then function as a DR box for the remote site.

I then want to use replication from the DR box to our other (reporting) SQL servers in London.

The idea is to automate our currently manual BCP processes and trikle feed data to our servers throughout the day - thus keeping them up to date.

On the surface does this look like a good idea and is there any real reason why you might use a manual BCP over automated replication? As far as I know the data to the reporting SQL servers only needs to be read-only.
Not knowing too much about replication - can I replicate just selected tables from databases?

Any good documents on this are welcome also

Many thanks

FunkyDThe reason would be that in BCP case the most part of the job must be done manually. (without counting the horizontal filtering, that must be done each time you want to select your records - supposing you use "queryout" option)
On the other hand, the replication is smoother and is full automated.(and allows you, of course, to select only the tables you want)

If you want to, I can send you extra-documentation from Microsoft SQL Server 2000 System Administration Training Kit

Originally posted by FunkyD
I have 2 SQL servers at a remote site and currently we FTP BCP data to our London site that is then BCP into other SQL databases.

I am wanting to simplify this and get rid of all the batch files we have and do the following...

Log ship from the remote site to London over the internet. The log shipping server can then function as a DR box for the remote site.

I then want to use replication from the DR box to our other (reporting) SQL servers in London.

The idea is to automate our currently manual BCP processes and trikle feed data to our servers throughout the day - thus keeping them up to date.

On the surface does this look like a good idea and is there any real reason why you might use a manual BCP over automated replication? As far as I know the data to the reporting SQL servers only needs to be read-only.
Not knowing too much about replication - can I replicate just selected tables from databases?

Any good documents on this are welcome also

Many thanks

FunkyD|||We are using SQL 7 so it might not be the same as for SQL 2000? I figure that for moving data around we are better off using replication instead of BCP. I'm just not experienced enough in these areas to know whether this is the case or not

Originally posted by dbadelphes
The reason would be that in BCP case the most part of the job must be done manually. (without counting the horizontal filtering, that must be done each time you want to select your records - supposing you use "queryout" option)
On the other hand, the replication is smoother and is full automated.(and allows you, of course, to select only the tables you want)

If you want to, I can send you extra-documentation from Microsoft SQL Server 2000 System Administration Training Kit

can i remove visual studio after sql 2005 install?

it's been a while since i installed sql2005, but doesn't visual studio get installed at the same time? all the servers that i installed sql2005 on have visual studio on them too. the sysadmins think having VS on the servers is a security risk and want to remove it. if we remove VS from the servers, will that impact SQL Server 2005?

If you have the SQL Server 2005 tools installed you can not remove Visual Studio from the server. The SQL Server 2005 tools are based on the Visual Studio IDE making it required to have the tools.

Can I register SQL 2005 Server in the SQL 2000 Enterprise Manager?

Hi All,
I was wondering if I could register SQL 2005 Server in the SQL 2000
Enterprise Manager or vice versa.
I have two database servers. One of them is SQL 2000 enterprise edition
and the other one is SQL 2005 developer edition. We have not moved
completely to our new server from our old SQL 2000 server as we are
still learning and testing features.
I will highly appreciate your suggestions.
Thanks a million in advance.
Best regards,
MamunYou can manager 2000 and 2005 in 2005 Management Studio.
You can manage 7.0 and 2000 in 2000 Enterprise Manager.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"microsoft.public.dotnet.languages.vb" <mamun_ah@.hotmail.com> wrote in messa
ge
news:1144955476.589607.315160@.v46g2000cwv.googlegroups.com...
> Hi All,
> I was wondering if I could register SQL 2005 Server in the SQL 2000
> Enterprise Manager or vice versa.
> I have two database servers. One of them is SQL 2000 enterprise edition
> and the other one is SQL 2005 developer edition. We have not moved
> completely to our new server from our old SQL 2000 server as we are
> still learning and testing features.
> I will highly appreciate your suggestions.
> Thanks a million in advance.
> Best regards,
> Mamun
>|||You are suggested to use SQL Server Management Studio as it supports SQL
2000 and provides better perfomance when compared to the Enterprise Manager
in SQL 2000.
Martin C K Poon
Senior Analyst Programmer
====================================
"microsoft.public.dotnet.languages.vb" <mamun_ah@.hotmail.com> ?
news:1144955476.589607.315160@.v46g2000cwv.googlegroups.com ?...
> Hi All,
> I was wondering if I could register SQL 2005 Server in the SQL 2000
> Enterprise Manager or vice versa.
> I have two database servers. One of them is SQL 2000 enterprise edition
> and the other one is SQL 2005 developer edition. We have not moved
> completely to our new server from our old SQL 2000 server as we are
> still learning and testing features.
> I will highly appreciate your suggestions.
> Thanks a million in advance.
> Best regards,
> Mamun
>

Can I link 2 tables from 2 different SQL Servers ?

I know that 2 tables from 2 databases can be join together. But how about 2 tables from 2 databases which are store separately on 2 different SQL servers . Can this be done ?You can create a linked server and join the tables using the 4 part sytax

select *
from svr1.db1.owner1.tbl1 tbl1
join svr2.db2.owner2.tbl2 tbl2
on tbl1.fld1 = tbl2.fld2

Be careful though as the data will have to be sent to one of the servers to do the join.
Setting collation compatability for the linked server will also affect this.|||Will this effect the performance of the servers ?

Will joining 2 SQL servers improve the performance of a query that was previously having performance problems ?|||>> Be careful though as the data will have to be sent to one of the servers to do the join.

It will probably be very slow.