February 22, 2012 at 3:03 pm
Does anyone have both SSRS 2005 & 2008 in their Corporate Environment?
If so how do you mange it?
I want to move to 2008R2 but not everyone is on board. We are segregated by Functional area, (BI/DW, Web Applications, OLTP)
I would appreciate your sharing your experiences.
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
February 22, 2012 at 3:21 pm
Welsh Corgi (2/22/2012)
Does anyone have both SSRS 2005 & 2008 in their Corporate Environment?If so how do you mange it?
I want to move to 2008R2 but not everyone is on board. We are segregated by Functional area, (BI/DW, Web Applications, OLTP)
I would appreciate your sharing your experiences.
Yes - we have both and it is due to political lines.
We are trying to get the 2005 upgraded to 2008. It would mean easier management and deployment if we had a single version.
For now, we maintain separate report code bases for the different versions.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
February 22, 2012 at 3:25 pm
SQLRNNR (2/22/2012)
Welsh Corgi (2/22/2012)
Does anyone have both SSRS 2005 & 2008 in their Corporate Environment?If so how do you mange it?
I want to move to 2008R2 but not everyone is on board. We are segregated by Functional area, (BI/DW, Web Applications, OLTP)
I would appreciate your sharing your experiences.
Yes - we have both and it is due to political lines.
We are trying to get the 2005 upgraded to 2008. It would mean easier management and deployment if we had a single version.
For now, we maintain separate report code bases for the different versions.
Thanks Jason.
If I understand you correctly, as far as Administration is concerned, the Reporting Services Server would have to be 2008 R2 and you would have both 2005 & 2008 R2 Code versions to maintain.
I could not have a 2005 Reporting Sever with 2008 R2 Code?
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
February 22, 2012 at 4:03 pm
I was thinking, just because the back end databases are moved to SQL Server 2008 R2 does not prevent me from creating SSIS & SSRS Packages using BIDS 2005.
Do you concur?
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
February 23, 2012 at 4:57 am
SQLRNNR (2/22/2012)
Welsh Corgi (2/22/2012)
Does anyone have both SSRS 2005 & 2008 in their Corporate Environment?If so how do you mange it?
I want to move to 2008R2 but not everyone is on board. We are segregated by Functional area, (BI/DW, Web Applications, OLTP)
I would appreciate your sharing your experiences.
Yes - we have both and it is due to political lines.
We are trying to get the 2005 upgraded to 2008. It would mean easier management and deployment if we had a single version.
For now, we maintain separate report code bases for the different versions.
How much does it complicate the management and deployment process? Please cite specific examples.
My intent was to continue to use SSIS & SSRS 2005 and just convert the Backend Database.
Thanks.
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
February 23, 2012 at 10:23 am
You need to have both the 2005 and 2008 visual studio components installed. Devs must remember to not upgrade any 2005 projects else they will fail when deployed to 2005.
The added layer of administration between keeping the projects separate.
The extra maintenance needed to manage the extra instances
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
February 23, 2012 at 10:41 am
Welsh Corgi (2/22/2012)
I was thinking, just because the back end databases are moved to SQL Server 2008 R2 does not prevent me from creating SSIS & SSRS Packages using BIDS 2005.Do you concur?
That is correct. But if somebody opens those projects in BIDS 2008 then an upgrade to the package will be prompted. People have to be careful not to upgrade the package.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
February 23, 2012 at 10:42 am
Welsh Corgi (2/22/2012)
SQLRNNR (2/22/2012)
Welsh Corgi (2/22/2012)
Does anyone have both SSRS 2005 & 2008 in their Corporate Environment?If so how do you mange it?
I want to move to 2008R2 but not everyone is on board. We are segregated by Functional area, (BI/DW, Web Applications, OLTP)
I would appreciate your sharing your experiences.
Yes - we have both and it is due to political lines.
We are trying to get the 2005 upgraded to 2008. It would mean easier management and deployment if we had a single version.
For now, we maintain separate report code bases for the different versions.
Thanks Jason.
If I understand you correctly, as far as Administration is concerned, the Reporting Services Server would have to be 2008 R2 and you would have both 2005 & 2008 R2 Code versions to maintain.
I could not have a 2005 Reporting Sever with 2008 R2 Code?
No. 2008 R2 reports will not work in SSRS 2005 (changes to tables and matrices now being tablixes).
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
February 23, 2012 at 4:07 pm
Jason,
Thanks for your responses.
The intent was to keep the SSIS Packages & Reports in 2005.
I made the mistake not knowing any better of opening an SSIS Package in 2008. Fortunately I had a backup and was able to recover.
Thanks again!
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
February 26, 2012 at 3:29 pm
I have 2005 / 2008 /2008 R2 OLTP databases and 2008 / 2008 R2 SSRS instances.
It doesn't really matter what the source database is, you can run SSRS or SSIS against an Oracle database if you really want to.
Unless you're talking about the SSRS database that runs the report manager & stores all the reports & subscriptions etc. I've never tried using BIDS 2005 to store reports in a 2008 SSRS instance. The other way around definitely doesn't work. You can easily run multiple versions of BIDS on your dev machines.
The only place I have run into difficulty is using spatial data types which won't work against a 2005 database.
Meanwhile 2012 is about to be released so I won't be upgrading anything to 2008 R2 at all, and I'll wait until 2012 hits a stable version.
February 27, 2012 at 4:19 am
Up until November last year we had a mixed SQL 2005 and SQL 2008 R2 environment.
We direct all database writes for our critical systems to a central server and replicate the data out to a number of 'read-only' servers to satisfy our web traffic. Typically the central write server is the last to get upgraded to a new release.
The main justification for doing the upgrade was risk reduction. SQL 2005 is now out of mainstream support and the skill base for troubleshooting it is declining. We estimated that remaining on SQL 2005 would result in 1 outage per year more than if we moved to the latest supported version where our skills were highest. When the cost of the outage was taken into account, this justification more than paid the costs of the upgrade.
The main intangible benefit was that we would be able to quickly exploit new technology associated with SQL 2008 R2 if we had it available. It is very difficult to put a monetry value on this type of benefit, but we have been bitten in the past by being unable to exploit a business opportunity in the desired time to market because we had not upgraded some other software. This makes our management more aware of this type of problem.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
February 27, 2012 at 9:25 am
Reports written using BIDS 2005 can be run on a 2008 server. I can't remember if I deployed the report from BIDS or pulled it in from the report manager but I've done it.
Always install the 2005 tools before the 2008 ones as going backwards doesn't work.
February 27, 2012 at 2:58 pm
We run both versions, but all of the reports hosted on ssrs 2008 are written in BIDS 2005.
One issue that we ran into concerns deployment of the ActiveX Client Print control. In our environment regular users are not Local PC Admins, so the normal CAB installation of the print control does not occur. We had to create installation scripts to deploy both the 2005 and 2008 client print controls to users workstations.
Viewing 13 posts - 1 through 12 (of 12 total)
You must be logged in to reply to this topic. Login to reply