Multi-Server setup: RS, Sharepoint, new SP2 Webparts

I was reading the SP2 readme and I see this in section 4.1.1:
"To use the Reporting Services SharePoint Web parts, Report Server and
Report Manager must both be installed."
My company's RS server is on it's own box (A). The RS Configuration db
is on it's own box (B). Our intranet (Sharepoint) site is on it's own
box (C). 3 servers total. I want to try out the 2 new web parts. Can I
just copy the the RSWebParts.cab from server A to our Sharepoint server
C and install it or do I actually have to install a full blown
installation of RS plus RS SP2 on that Sharepoint server C? If so, why?
Because I was planning to point the web parts to the reports that exist
on the separate RS server A, or is that not permitted?
Am I going to have to redeploy my reports to C, manage a second
configuration database / report server? I hope not.
Thank you!No, you do not need to install RS on Box C. The parts can be pointed to any
existing RS. The point of the documentation was to let people know they
needed a working RS for the parts to work, not that they needed to all exist
on the same box.
I hope that helps.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Dave" <macleary2000@.yahoo.com> wrote in message
news:1134065827.784617.228020@.g44g2000cwa.googlegroups.com...
>I was reading the SP2 readme and I see this in section 4.1.1:
> "To use the Reporting Services SharePoint Web parts, Report Server and
> Report Manager must both be installed."
> My company's RS server is on it's own box (A). The RS Configuration db
> is on it's own box (B). Our intranet (Sharepoint) site is on it's own
> box (C). 3 servers total. I want to try out the 2 new web parts. Can I
> just copy the the RSWebParts.cab from server A to our Sharepoint server
> C and install it or do I actually have to install a full blown
> installation of RS plus RS SP2 on that Sharepoint server C? If so, why?
> Because I was planning to point the web parts to the reports that exist
> on the separate RS server A, or is that not permitted?
> Am I going to have to redeploy my reports to C, manage a second
> configuration database / report server? I hope not.
> Thank you!
>

Multiple Table Grouping

Hi,
I have two tables based on the same dataset.
The way the report is setup i have it set up with two tables.
One table shows the latest month and the other table shows a 12 month period
of the same data.
It is also grouped by division number.
What i want to do is show both tables (latest and 12 month) for division A
then a page break and then both tables for division B.
Can this be done.Yes, but AFAIK only with 4 Tables. Two for div a and two for div b.
Another thing would be to put the tables horizontally together (in a
retangle ) and do your page break on a group basis.
HTH, Jens Suessmeyer.
--
http://www.sqlserver2005.de
--
"Fez" <Fez@.discussions.microsoft.com> schrieb im Newsbeitrag
news:702B1045-289B-41DF-A8D0-83A570389534@.microsoft.com...
> Hi,
> I have two tables based on the same dataset.
> The way the report is setup i have it set up with two tables.
> One table shows the latest month and the other table shows a 12 month
> period
> of the same data.
> It is also grouped by division number.
> What i want to do is show both tables (latest and 12 month) for division A
> then a page break and then both tables for division B.
> Can this be done.|||Well the reason i have two tables is because of the size of the inforamtion.
I have to split the data up into 2 tables.

MULTIPLE SQL INSTANCES

SQL 2K / WINDOWS 2003 SERVER
I have a box with 2 SQL INSTANCES and each instances with few databases.
Memory is setup to 'Use a fix memory size' and setup with half and one GB
each .
Almost 250 GB free hard-disk space and both instances using 4 processors.
I have different SQL jobs running on each instances.
My issue is , few jobs which usually runs within 4-5 hrs, running for 12-15
hrs and this is not happening always.
Checked for SQL LOCKS and found NONE.
Please advice me , how to trouble-shoot this ?
Rgds
MS-USER
Hi
Without knowing the nature of the jobs it is hard to give detailed advice,
but I would start by looking at performance monitor and try and see if there
is a bottleneck. Your may well have contention on the discs as this is a
common resource that each instance will be competing with, therefore disc
queue lengths, also if your logs and data are on the same set of discs there
potentially there would be problems even with a single instance. Another area
that may cause problems is processor affinity. You may want to change the
affinity mask and see if that helps or use the MAXDOPS hint on your queries.
You may want to read the SQL Server 2000 Performance Tuning Technical
Reference Manual ISBN ISBN 0-7356-1270-6 and Inside SQL Server 2000 by Kalen
Delaney ISBN 0-7356-0998-5
John
"MS User" wrote:

> SQL 2K / WINDOWS 2003 SERVER
> I have a box with 2 SQL INSTANCES and each instances with few databases.
> Memory is setup to 'Use a fix memory size' and setup with half and one GB
> each .
> Almost 250 GB free hard-disk space and both instances using 4 processors.
> I have different SQL jobs running on each instances.
> My issue is , few jobs which usually runs within 4-5 hrs, running for 12-15
> hrs and this is not happening always.
> Checked for SQL LOCKS and found NONE.
> Please advice me , how to trouble-shoot this ?
> Rgds
> MS-USER
>
>

MULTIPLE SQL INSTANCES

SQL 2K / WINDOWS 2003 SERVER
I have a box with 2 SQL INSTANCES and each instances with few databases.
Memory is setup to 'Use a fix memory size' and setup with half and one GB
each .
Almost 250 GB free hard-disk space and both instances using 4 processors.
I have different SQL jobs running on each instances.
My issue is , few jobs which usually runs within 4-5 hrs, running for 12-15
hrs and this is not happening always.
Checked for SQL LOCKS and found NONE.
Please advice me , how to trouble-shoot this '
Rgds
MS-USERHi
Without knowing the nature of the jobs it is hard to give detailed advice,
but I would start by looking at performance monitor and try and see if there
is a bottleneck. Your may well have contention on the discs as this is a
common resource that each instance will be competing with, therefore disc
queue lengths, also if your logs and data are on the same set of discs there
potentially there would be problems even with a single instance. Another area
that may cause problems is processor affinity. You may want to change the
affinity mask and see if that helps or use the MAXDOPS hint on your queries.
You may want to read the SQL Server 2000 Performance Tuning Technical
Reference Manual ISBN ISBN 0-7356-1270-6 and Inside SQL Server 2000 by Kalen
Delaney ISBN 0-7356-0998-5
John
"MS User" wrote:
> SQL 2K / WINDOWS 2003 SERVER
> I have a box with 2 SQL INSTANCES and each instances with few databases.
> Memory is setup to 'Use a fix memory size' and setup with half and one GB
> each .
> Almost 250 GB free hard-disk space and both instances using 4 processors.
> I have different SQL jobs running on each instances.
> My issue is , few jobs which usually runs within 4-5 hrs, running for 12-15
> hrs and this is not happening always.
> Checked for SQL LOCKS and found NONE.
> Please advice me , how to trouble-shoot this '
> Rgds
> MS-USER
>
>

MULTIPLE SQL INSTANCES

SQL 2K / WINDOWS 2003 SERVER
I have a box with 2 SQL INSTANCES and each instances with few databases.
Memory is setup to 'Use a fix memory size' and setup with half and one GB
each .
Almost 250 GB free hard-disk space and both instances using 4 processors.
I have different SQL jobs running on each instances.
My issue is , few jobs which usually runs within 4-5 hrs, running for 12-15
hrs and this is not happening always.
Checked for SQL LOCKS and found NONE.
Please advice me , how to trouble-shoot this '
Rgds
MS-USERHi
Without knowing the nature of the jobs it is hard to give detailed advice,
but I would start by looking at performance monitor and try and see if there
is a bottleneck. Your may well have contention on the discs as this is a
common resource that each instance will be competing with, therefore disc
queue lengths, also if your logs and data are on the same set of discs there
potentially there would be problems even with a single instance. Another are
a
that may cause problems is processor affinity. You may want to change the
affinity mask and see if that helps or use the MAXDOPS hint on your queries.
You may want to read the SQL Server 2000 Performance Tuning Technical
Reference Manual ISBN ISBN 0-7356-1270-6 and Inside SQL Server 2000 by Kalen
Delaney ISBN 0-7356-0998-5
John
"MS User" wrote:

> SQL 2K / WINDOWS 2003 SERVER
> I have a box with 2 SQL INSTANCES and each instances with few databases.
> Memory is setup to 'Use a fix memory size' and setup with half and one GB
> each .
> Almost 250 GB free hard-disk space and both instances using 4 processors.
> I have different SQL jobs running on each instances.
> My issue is , few jobs which usually runs within 4-5 hrs, running for 12-1
5
> hrs and this is not happening always.
> Checked for SQL LOCKS and found NONE.
> Please advice me , how to trouble-shoot this '
> Rgds
> MS-USER
>
>

Multiple Servers in ODBC Client Setup

OK, something weird is happening.
I have a standard Windows XP client and I am trying to set up a simple ODBC
entry. So I go to Control Panel/Administrative Tools/ODBC/System Tab. From
there I create a new ODBC entry connecting to a SQL Server. I enter in the
name of my ODBC and a descripton. When I hit the drop-down button to select
a server I see my 2 SQL Server machines (local machine also named "Jim" and
sbserver) but they are listed twice or even 3 times (see below) and the local
machine has even more entries. What gives and how do I clean this up? Both
seem to work when I "test" at the last step but I have a local application
using this ODBC and it is failing to run so I think it is having "issues"
with these multiple entries.
Thanks!
-Richard
e.g.
(local)
(local)
Jim
Jim
jim
sbserver
sbserver
Make sure your MDAC installation isn't flaky - you can use
component checker to verity the MDAC version and
installation. You can download the tool from:
http://msdn2.microsoft.com/en-us/data/aa937730.aspx
How many instances do you have on each of those servers?
Do you get the same list if you execute the following from
the command prompt:
osql -L
-Sue
On Fri, 16 Mar 2007 04:47:05 -0700, Richard K
<RichardK@.discussions.microsoft.com> wrote:

>OK, something weird is happening.
>I have a standard Windows XP client and I am trying to set up a simple ODBC
>entry. So I go to Control Panel/Administrative Tools/ODBC/System Tab. From
>there I create a new ODBC entry connecting to a SQL Server. I enter in the
>name of my ODBC and a descripton. When I hit the drop-down button to select
>a server I see my 2 SQL Server machines (local machine also named "Jim" and
>sbserver) but they are listed twice or even 3 times (see below) and the local
>machine has even more entries. What gives and how do I clean this up? Both
>seem to work when I "test" at the last step but I have a local application
>using this ODBC and it is failing to run so I think it is having "issues"
>with these multiple entries.
>Thanks!
>-Richard
>e.g.
>(local)
>(local)
>Jim
>Jim
>jim
>sbserver
>sbserver