Another USe case.

I have multiple parameterized SP for our Application.

When I Executes those SP individual it will returns output within 1 Sec. But when we are running Test Load...

This is probably a couple of stupid questions that shows my ignorance, but if you never ask how will you learn... 🙂

1. Why are you doing your updates in batches?...

Not to be left out, here's my take on a possible solution: 🙂

DROP TABLE IF EXISTS #testdata;

CREATE TABLE #testdata -- Source data structure as specified by OP...
(
...

Just a thought... have you tried to change the driver on your connection in the package?

If you're using OLE DB, then you're most likely using the old "SQL Server Native...

I don't know that we know that it's Social Security Numbers in clear text, do we? We only know that the name of the column is SSN, I think. It...

This would return NULL if the SSN existed only in the third table (for example). Not what the OP requires, I believe.

Yes, well that's the question, isn't it? I wouldn't...

I shouldnt have a problem joining the tables but my main concern was when i get to the end and write the where filter clause do I have to ask...

• This reply was modified 2 years, 1 month ago by  kaj.

hmmm... I would probably use a Derived Column transformation:

(DT_NUMERIC,20,2)(REPLACE(REPLACE([EuropeanVarcharAmount],".",""),",","."))

or something like that...

An example of a Stored Procedure where an output parameter could be used would be where the caller request a dataset be returned based on some input parameters, but at...

One must apparently be very careful with certain words here. I posted a reply which I subsequently edited to include a comment about me a busing (one word) CROSS APPLY...

;WITH myTable AS (SELECT * FROM (VALUES ('3#5'),('8063#0018375'),('8063#018375'),('063#018375'),('063invalid018375')) X(AccountNumber)) 
SELECT 
t.AccountNumber, 
lrp.LeftMostAccountNumberPart,
lrp.RightMostAccountNumberPart,
fp.AdjustedAccountID
FROM myTable t
CROSS APPLY (
SELECT 
CHARINDEX('#', t.AccountNumber) AS sepPos, 
LEN(t.AccountNumber) AS accLen
) sp
CROSS APPLY (
SELECT 
RIGHT('0000'...

;WITH myTable AS (SELECT * FROM (VALUES ('3#5'),('8063#0018375'),('8063#018375'),('063#018375'),('063invalid018375')) X(AccountNumber)) 
SELECT 
t.AccountNumber, 
lrp.LeftMostAccountNumberPart,
lrp.RightMostAccountNumberPart,
fp.AdjustedAccountID
FROM myTable t
CROSS APPLY (
SELECT 
CHARINDEX('#', t.AccountNumber) AS sepPos, 
LEN(t.AccountNumber) AS accLen
) sp
CROSS APPLY (
SELECT 
RIGHT('0000'...

• This reply was modified 2 years, 11 months ago by  kaj.
• This reply was modified 2 years, 11 months ago by  kaj.
• This reply was modified 2 years, 11 months ago by  kaj.
• This reply was modified 2 years, 11 months ago by  kaj.

I'm guessing this has to do with the new  Cardinality Estimator that was introduced with SQL Server 2014.

We've seen some strange goings on with this feature if the statistics aren't...

Never done it, but if you have CLR enabled, you might be able to use that instead of the old VBScript functions.

https://sqlsunday.com/2013/03/03/web-requests-using-clr-proc/