the code you posted is not creating the table SystemDateTable

i assume what you psoted is just a portion of what you are doing, right?

in what you did paste, you are...

you should be able to find what the issue is pretty easily;

if you change the object id below to the one you are looking for, what do you get?

on my...

your variable is too small

DECLARE @sql nvarchar(1000)

but the code you pasted is at least 1065 chars, depending on t table name.

change it to nvarchar(max) to be safe and try again.

some of your dates are not dates...probably blank strings for death date(a reasonable assumption would be not all patients die or get transferred)

something like this:

...

CASE

WHEN ISDATE(SUBSTRING(BulkColumn, 41, 8)) =1

THEN...

since you have everything in a staging table, shouldn't you just convert the columns explicitly?

-- Substring input patient

set @sql = N'SELECT

CONVERT(int,SUBSTRING(BulkColumn, 1, 4)) AS patid

,SUBSTRING(BulkColumn, 5, 1) AS...

I'm guessing the new columns( with defaults or not?) caused a lot of page splits of the data.

I'm thinking rebuilding the indexes on the table would improve the perforamnce...

Shurkadze (8/22/2011)

---

What if you have a row modified in OLTP with a column value changed that is not mapped to DW. The data then should not be moved to Data...

Gail I was looking more for a rule of thumb, I'm sure that just like you identified, there are exceptions where the key lookup is better...testing would...

you rename the Server at the operating system/networking level, not the instances themselves.

any...

wouldn't you simply do the following.

1. Rename the existing SQL123 to, say SQL123CLUSTER

2. change the ip address on the SQL123CLUSTER to a different IP address.

3. enable clustering, and give...

Ninja's_RGR'us (8/22/2011)

---

I would ignore the where completely unless I'd know only a small % of the rows would get updated.

This will do a table scan anyways. So you might...

the examples above (admittedly they are from 2007) suggested using a global temp table. i base dmy example fof of the previous...

i think you want to use IF EXISTS:

IF EXISTS (select * from ##result)

BEGIN

EXEC msdb.dbo.sp_send_dbmail

@recipients=N'emailaddress',

@body='The IP address with over...

nope not possible. a column must be identified, and it's new value identified for a valid UPDATE TABLE statement.

...but...you can use the table's metadata to generate the commands for you.

SELECT...

my advice is you are looking for a problem that does not exist. leave the statistics alone, and update them often.

statistics are used by the system to find the data...