Good deal, if you have any questions let me know.

CEWII

Why don't you take a look at these articles:

http://www.sqlservercentral.com/Authors/Articles/Elliott__Whitlow_/483442/%5B/url%5D

CEWII

You are very welcome.

CEWII

I think the relevant word is "compatibility", which I don't read as SQL 2000 mode, but more along the lines of SQL 2000 rules.

What I mean is that you are...

I have not run accross that error before during setup..

I would look in connect.microsoft.com to see if its a known issue..

I would perform a memory check using any tools...

A master key key and a cert are a step in encrypting SOME of your data. But only a small part which by themselves will not encrypt anything automagically.

When...

Yes the second parameter would be 1 for Parameter Name, the -1 as I understand it means to determine it automagically.. I rarely change that..

Assuming you are using a Exec SQL task.

Command would be:

EXEC dbo.domProductCategory_LoadMerge ?

GO

On the Exec SQL Task, Parameter Mapping Tab, click add

For Variable Name Select: System::PackageName

Direction: Input

Data Type: varchar

Paramter Name: 0...

They are generated within the product. In most cases automatically. This varies by product.

CEWII

Thats funny, I have that exact same article hanging on the wall of my cubie, from when I used to get these all the time..

CEWII

I think so.

CEWII

Just add a parameter to the sproc for that data and map the package variable into the parameter.

CEWII

Still happens in SQL 2008..

CEWII

I'm with GSquared on this one, personally I like !=, it feels more explicit as opposed to <> which feels less so, but is common in many other languages. ...

You might look at:

http://nclsqlinv.codeplex.com/%5B/url%5D

I know it isn't quite there yet, but its a good start..

CEWII