August 29, 2008 at 12:41 pm
Have you tried running the SSIS packages in scheduled jobs? Or are you just running them in Visual Studio?
The reason I ask is because Visual Studio (and Business Intelligence Dev Studio) don't actually use the SSIS engine from the SQL server when they run SSIS packages internally. They have their own runtime for them.
When you deploy the SSIS package to the server and try to run it as a job, it's a whole different story.
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
August 29, 2008 at 12:52 pm
Thanks for replying,
I am running packages directly in Visual Studio. Workgroup edition apparently does not allow me to schedule SSIS packages.
Does this mean I can still have full SSIS functionality (including fuzzy transformations) if I run the packages in Visual Studio?
In my case, running the packages manually would be a small cost compared to paying a full enterprise edition...
August 29, 2008 at 2:26 pm
If running them in VS works for you, there's no reason not to do it.
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
Viewing 3 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply