December 12, 2009 at 4:07 pm
Committed myself to SSIS. Spent the last week learning as I developed a beautiful package that executes flawlessly on my SQL 2008 Development box, ONLY to find out that it can't run on my Production Server because it's SQL2005! Help!
I'd LOVE to bump this server up from 05 to 08, but I'm just not sure that's an option for me at the moment.
Am I going to have to port the package to SQL2005? Any ideas out there? Can I install just SSIS 2008 on the SQL2005 server? The installer seems like it supports that.
.
December 13, 2009 at 1:23 am
As you have noticed, you need to "downgrade" your package to SSIS 2005 runtime level, if even possible (because of new features in SSIS2008).
How ?
IMO it is just better to develop your package in its tightly coupled BIDS environment.
Or (as you stated) prepare an SSIS environment for each BIDS version you have (and prepare upgrade scenarios for your dev teams, operational packages, ...).
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
December 13, 2009 at 6:52 am
Note also that the VBScript calls to external references have changed slightly as well.
[font="Times New Roman"]-- RBarryYoung[/font], [font="Times New Roman"] (302)375-0451[/font] blog: MovingSQL.com, Twitter: @RBarryYoung[font="Arial Black"]
Proactive Performance Solutions, Inc. [/font][font="Verdana"] "Performance is our middle name."[/font]
December 13, 2009 at 7:00 am
BrainMan (12/12/2009)
Can I install just SSIS 2008 on the SQL2005 server? The installer seems like it supports that.
Actually, I do think that you can do this. Note that SSIS installations are not "instanced" like the rest of SQL Server, however, the execution platform actually needs very little in order to run SSIS. In fact, all it really needs is the DTExec.exe image and the RTL's to run it, it doesn't even need a SQL Server installation (if I recall correctly).
And the SSIS Service is only used for storing the packages into SQL Server. If you store your packages to the file system instead, you wouldn't need that piece. The package deployer/installer is also optional, I never use it myself, I just copy the packages to their file store directories.
[font="Times New Roman"]-- RBarryYoung[/font], [font="Times New Roman"] (302)375-0451[/font] blog: MovingSQL.com, Twitter: @RBarryYoung[font="Arial Black"]
Proactive Performance Solutions, Inc. [/font][font="Verdana"] "Performance is our middle name."[/font]
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply