How to Resolve a BIDS 2005 and SQL Server 2008 Compatibility Issue

SQLServerCentral is supported by Red Gate Software Ltd.

Popular Topics

Home

Members

Calendar

Who's On

Home » Article Discussions » Article Discussions by Author » Discuss content posted by Mohan Kumar » How to Resolve a BIDS 2005 and SQL Server...

How to Resolve a BIDS 2005 and SQL Server 2008 Compatibility Issue

Rate Topic

Display Mode

Topic Options

Author

Message

Mohan Kumar

Posted Thursday, August 13, 2009 12:18 AM

Ten Centuries

Group: General Forum Members
Last Login: Thursday, January 03, 2013 4:44 PM
Points: 1,336, Visits: 595

Comments posted to this topic are about the item How to Resolve a BIDS 2005 and SQL Server 2008 Compatibility Issue

--www.sqlvillage.com

Post #769892

sibir1us

Posted Thursday, August 13, 2009 1:21 AM

Grasshopper

Group: General Forum Members
Last Login: Sunday, March 24, 2013 12:47 PM
Points: 21, Visits: 291

Thank you for the great article. I am sure that many will find it helpful. Recently I had some problems with my BI studio myself: I had created a SSRS report in 2005, and under no condition would that report run under 2008. A very sad story. I ended up re-creating the same report in 2008 just so I can release it...

Make everything as simple as possible, but not simpler.
Albert Einstein

Post #769927

cmille19

Posted Thursday, August 13, 2009 6:00 AM

SSC Veteran

Group: General Forum Members
Last Login: Thursday, May 16, 2013 5:46 AM
Points: 257, Visits: 671

Seems like a lot of trouble to go through. A better option would be to stand up a new 2008 test/upgrade environment on another server to allow developers to continue to support 2005 with their existing development environment. Alternatively if this is not possible, promote 2005 development to 2008 and leave the QA environment on 2005 to match production. The new 2008 replaces existing development upon production upgrade. QA is then upgraded shortly after production.

Post #770067

Cédric Dolain

Posted Thursday, August 13, 2009 6:53 AM

Ten Centuries

Group: General Forum Members
Last Login: Thursday, May 16, 2013 7:24 AM
Points: 1,406, Visits: 60

Instead of creating new SPs (with old names) calling the existing ones (with new names), it would be better to create synonyms...

Post #770106

kevin goux

Posted Thursday, August 13, 2009 7:56 AM

SSC Rookie

Group: General Forum Members
Last Login: Today @ 7:41 AM
Points: 30, Visits: 154

I had to add the following stored procedure to be able to save in SSIS package

CREATE PROCEDURE [dbo].[sp_dts_getfolder]
@name sysname,
@parentfolderid uniqueidentifier
AS
SELECT
folder.folderid,
folder.foldername,
folder.parentfolderid,
parent.foldername
FROM
sysssispackagefolders folder
LEFT OUTER JOIN
sysssispackagefolders parent
ON
folder.parentfolderid = parent.folderid
WHERE
folder.foldername = @name AND
(folder.parentfolderid = @parentfolderid OR
(@parentfolderid IS NULL AND folder.parentfolderid IS NULL))

Post #770170

SanjayAttray

Posted Thursday, August 13, 2009 11:38 AM

Hall of Fame

Group: General Forum Members
Last Login: Friday, March 15, 2013 2:43 PM
Points: 3,924, Visits: 1,554

Good info. Still reeling under 2005 and only got couple of Dev servers in 2008. But it's good to know info before in time.

SQL DBA.

Post #770367

larryq

Posted Wednesday, February 17, 2010 5:17 PM

Forum Newbie

Group: General Forum Members
Last Login: Monday, July 19, 2010 2:42 PM
Points: 3, Visits: 7

Thanks for the article-- this was a lifesaver for me.

Same scenario as you, I believe: SQL2008 database but SQL 2005 SSIS packages that needed to be run. It's absurd that you had to create all those aliases; didn't Microsoft have any backward compatibility in mind on this subject?

Post #867635

« Prev Topic | Next Topic »

Permissions