the issue is around your other variables being included in the concatenation. so, instead of just saying:

and client_id = ' + @MyClientId + '

change it to read (I am guessing...

setup the entire statement as a string and concatenate your derived string into the statement. so, the following would be after your if statement to piece together the string:

declare

The Merge Transformation is similar to the Union All but it only takes two data sources and the data sources must be sorted.

The Merge Join does either an Inner, Left...

If I am reading this right, from your source, you have columns that are coming across as NULL that you want translated to blank before entering into your destination.

To do...

is remote connections allowed?

if you go to the server and navigate to the SQL Server 2005-->Configuration Tools-->SQL Surface Area Configuration and click on the link for Surface Area Configuration...

the issue is that the Excel Destination will not create a file on the fly, it needs the file to exist. Can you create a CSV file instead of an...

a couple of things to try:

from the project that created and deployed the project originally, can you open the project file and connect and browse the cube through bids? if...

here are the steps:

create a package, in the control flow, add a data flow task

create a connection to your sql server

in the data flow task, add a OLE DB Source...

ah, but it is not.

in the named calculation, because you added the coalesce code as the column, here is the sql that was being rendered:

SELECT ...

for my own curiousity, what was the complete query that you used in the named query to replace the original table?

the exists error is occurring because there are two values in the subquery. that example is only valid in the FROM clause of the overall SELECT statement for the table....

sorry for getting back to you a little late, i do not know if this is still an issue or not for you but this is what I see can...

this sounds to me that the join between table a and either b and\or c is returning more than one record. so, the contact id not enough to join between...

the approach i would take would be in the DSV, create a named query that combines the two fact tables together. then, you can bring in the named query into...

one thing to look at is to put a data viewer from the ole db source to the data conversion and ensure that your string value with the decimal point...