September 22, 2011 at 5:40 am
Hi,
I'm attempting to run a package with a fuzzy lookup in it. This fuzzy lookup runs in debug, but it does not run in a package. According to the internet this is because I am using x64 Standard Edition of SSIS.
My question is this: Is there any way round this and as an Adjunct to this, WHAT IS THE POINT of allowing you to run it in debug but NOT in a package?
September 22, 2011 at 8:05 am
mat.elkington (9/22/2011)
Hi,I'm attempting to run a package with a fuzzy lookup in it. This fuzzy lookup runs in debug, but it does not run in a package. According to the internet this is because I am using x64 Standard Edition of SSIS.
My question is this: Is there any way round this and as an Adjunct to this, WHAT IS THE POINT of allowing you to run it in debug but NOT in a package?
Seems like this is an open issue, with no resolution yet: http://connect.microsoft.com/SQLServer/feedback/details/488387/fuzzy-lookup-triggers-sqldumper-even-with-very-small-dataset-with-run64bitruntime-set-to-false
September 22, 2011 at 10:58 pm
The fuzzy lookup task is not available with Standard Edition. It is only available in Enterprise and Developer editions. So, there is no bug related to your issue. The product is working exactly as Microsoft designed it.
The reason it works in "debug" is that all features are available within Visual Studio. Visual Studio allows you to develop for any edition. You can set a property for the project to tell Visual Studio which edition you are developing for. I am not sure but it may warn you when you are using features that are not supported in the target environment.
September 23, 2011 at 12:32 am
Hi
I haven't check this but try to change run64bitruntime option in debugging properties.
It might help.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply