The BETWEEN is fine.

What error message are you getting?

So your stub would just be:

Create Procedure uspGetCustomerInfo

AS

[font="Courier New"]SELECT CONVERT(INT,NULL) AS PolicyID, CONVERT(VARCHAR(30),NULL) AS FirstName, CONVERT(VARCHAR(30),NULL) AS LastName

, CONVERT(DATETIME,NULL) AS LoadDate, CONVERT(INT,NULL) AS PolicyNumber, CONVERT(INT,NULL) AS StoreID

, CONVERT(INT,NULL) AS...

Ok - let me goa bit more step-by-step.

Say you have a procedure:

CREATE PROC MyProc

@Param1

AS

SET NOCOUNT ON

SELECT GETDATE() AS MyVal INTO #tmp

SELECT * FROM #tmp

--END MyProc

SSIS will hate the temp...

The optimizer does not really care much about the order of items in the WHERE clause when it generates the execution plan unless everything else is equal.

Since the tuning wizard...

I see your dilema - I don't think there is a good way of doing what you want.

Technically, the OLEDB Destination supports any T-SQL statement by using the Advanced Editor. It does not work well though. If you manage to get this to work, it...

I guess because I don't like multiple loops, I would have done this operation with only one loop container.

I would use a ForEach file loop container to loop through all...

dbcc useroptions

The tuning advisor is telling you that your performance would be better if your index was in the correct order for the query.

That does not mean the index there is...

If you created a maintenance plan for "All User Databases", it would pick up any newly added databases.

As an alternative, I suppose you could create a trigger that created a...

Using temp tables in your procedures can be a good idea in a lot of cases, but they cause some havoc with some of the included tools.

I create stubs at...

@State is declared NVARCHAR(2)

Setting it to 'All' actually makes it 'Al' and I don't think you want the Alabama information.

Make it 3 characters.

It's probably the temp table, not the CTE that is the problem.

When the parsing engine normally gets the meta-data for a stored procedure, it parses the statements rather than actually...

Ok - you're wrong.

The Merge Join options are INNER, LEFT, AND FULL OUTER.

I actually never noticed that you cannot do a RIGHT join with it, but I suppose you could...

It is probably because of a conversion from your data in your data flow.

Try converting the variable data in the data flow or right in the update:

"UPDATE MyTable SET MyField=COALESCE(MyField,'')+CONVERT(VARCHAR,?)...