Multi-team and Multi-Server deployment environment issue

ACK!
So, here I am at my new job, thinking I'm learning RS because they have it
deployed in their environment, only to find out that I'm a member of one of
the teams *expected* to deploy it in the near future...
Due to SOX (Sarbane-Oxley) and other issues, we're going to have 3 servers:
Development, QC and Production.
There are also three teams: Development, QC and Production. I'm a member of
the Dev team. We have to figure out a way to deploy the Reports to the Dev
server for development, then allow the QC team to deploy the reports from the
Dev server to the QC server for testing, and finally to allow the Prod team
to deploy the reports from the QC server to the Production server without the
use of the Visual Studio .Net Deployment tool (since the Production team
doesn't have access, and likely the QC team doesn't either).
One of my co-workers is thinking he'll have to write a whole new app to
import the reports. The other option we can think of is the RS.exe script,
but that will require someone managing that script full time.
Does anyone have any other thoughts?
Thanks,
Catadmin
--
MCDBA, MCSA
Random Thoughts: If a person is Microsoft Certified, does that mean that
Microsoft pays the bills for the funny white jackets that tie in the back?
@.=)You may want to check the following tool courtesy of Jasper Smith:
http://www.sqldbatips.com/showarticle.asp?ID=62
-- Robert
This posting is provided "AS IS" with no warranties, and confers no rights.
"Catadmin" <goldpetalgraphics@.yahoo.com> wrote in message
news:7AD0D78A-682E-4904-8CF2-EA6AC04F6F7A@.microsoft.com...
> ACK!
> So, here I am at my new job, thinking I'm learning RS because they have it
> deployed in their environment, only to find out that I'm a member of one
> of
> the teams *expected* to deploy it in the near future...
> Due to SOX (Sarbane-Oxley) and other issues, we're going to have 3
> servers:
> Development, QC and Production.
> There are also three teams: Development, QC and Production. I'm a member
> of
> the Dev team. We have to figure out a way to deploy the Reports to the
> Dev
> server for development, then allow the QC team to deploy the reports from
> the
> Dev server to the QC server for testing, and finally to allow the Prod
> team
> to deploy the reports from the QC server to the Production server without
> the
> use of the Visual Studio .Net Deployment tool (since the Production team
> doesn't have access, and likely the QC team doesn't either).
> One of my co-workers is thinking he'll have to write a whole new app to
> import the reports. The other option we can think of is the RS.exe
> script,
> but that will require someone managing that script full time.
> Does anyone have any other thoughts?
> Thanks,
> Catadmin
> --
> MCDBA, MCSA
> Random Thoughts: If a person is Microsoft Certified, does that mean that
> Microsoft pays the bills for the funny white jackets that tie in the
> back?
> @.=)|||Thank you, Robert. I greatly appreciate the link.
Catadmin
--
MCDBA, MCSA
"When I get back, you're going to argue with me about the things that I want
to argue about!" Josh Lyman, The West Wing
"Robert Bruckner [MSFT]" wrote:
> You may want to check the following tool courtesy of Jasper Smith:
> http://www.sqldbatips.com/showarticle.asp?ID=62
> -- Robert
> This posting is provided "AS IS" with no warranties, and confers no rights.
> "Catadmin" <goldpetalgraphics@.yahoo.com> wrote in message
> news:7AD0D78A-682E-4904-8CF2-EA6AC04F6F7A@.microsoft.com...
> > ACK!
> >
> > So, here I am at my new job, thinking I'm learning RS because they have it
> > deployed in their environment, only to find out that I'm a member of one
> > of
> > the teams *expected* to deploy it in the near future...
> >
> > Due to SOX (Sarbane-Oxley) and other issues, we're going to have 3
> > servers:
> > Development, QC and Production.
> >
> > There are also three teams: Development, QC and Production. I'm a member
> > of
> > the Dev team. We have to figure out a way to deploy the Reports to the
> > Dev
> > server for development, then allow the QC team to deploy the reports from
> > the
> > Dev server to the QC server for testing, and finally to allow the Prod
> > team
> > to deploy the reports from the QC server to the Production server without
> > the
> > use of the Visual Studio .Net Deployment tool (since the Production team
> > doesn't have access, and likely the QC team doesn't either).
> >
> > One of my co-workers is thinking he'll have to write a whole new app to
> > import the reports. The other option we can think of is the RS.exe
> > script,
> > but that will require someone managing that script full time.
> >
> > Does anyone have any other thoughts?
> >
> > Thanks,
> >
> > Catadmin
> > --
> > MCDBA, MCSA
> > Random Thoughts: If a person is Microsoft Certified, does that mean that
> > Microsoft pays the bills for the funny white jackets that tie in the
> > back?
> > @.=)
>
>sql

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!
>

Multi-Server Jobs

Why is it that when viewing Multi-Server Jobs on the MSX Server via Management Studio (Server\SQL Agent\Jobs\Multi-Server Jobs), only jobs that are in the default [Uncategorized (Multi-Server)] category appear? Any other Multi-Server job that has been put into a different category is displayed under the Local Jobs folder.

A master server distributes jobs to, and receives events from, target servers. A master server also stores the central copy of job definitions for jobs that are run on target servers. Target servers connect periodically to the master server to update their schedule of jobs. If a new job exists on the master server, the target server downloads the job. After the target server completes the job, it reconnects to the master server and reports the status of the job.

So in this case if you haven't specified the job category then they are shown as default.

|||That still doesn't answer my question! All I was questioning was why when a job has been categorised in any other Multi-Server job category than [Uncategorized (Multi-Server)] it doesn't show under the Multi-Server jobs folder, (as it does in Enterprise Manager).|||Having dug around a little further it appears that this has already been raised as a bug and should be in SP2.|||

http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=139988

This will be addressed in the next service pack.

sql

Multi-Server Instance

What is the effect of deploying Multi-Server instance on performance?

Can you explain a bit more what you mean by a 'multi server instance'..?

/Kenneth

|||

Each host machine (server) can host (virtually) any number of SQL Server instances. Each instance has its own master, model and other support databases along with the user databases. Each instance consumes RAM and CPU cycles and while many of the SQL Server code DLLs are shared, there are instance memory allocations that cannot be shared. Each instance has its own cache to hold procedures, query plans and data--these cannot be shared. That is, each SQL Server instance competes with all other instances, the OS and all other running processes for RAM, disk and CPU resources. Does this tell you something about performance? It should.

See chapter 2 of my book "Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)" for more details.

Multi-Server Instance

What is the effect of deploying Multi-Server instance on performance?

Can you explain a bit more what you mean by a 'multi server instance'..?

/Kenneth

|||

Each host machine (server) can host (virtually) any number of SQL Server instances. Each instance has its own master, model and other support databases along with the user databases. Each instance consumes RAM and CPU cycles and while many of the SQL Server code DLLs are shared, there are instance memory allocations that cannot be shared. Each instance has its own cache to hold procedures, query plans and data--these cannot be shared. That is, each SQL Server instance competes with all other instances, the OS and all other running processes for RAM, disk and CPU resources. Does this tell you something about performance? It should.

See chapter 2 of my book "Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)" for more details.