This is basically The situation I have in my Data Flow:

Flat File

|

Derived Column

|

Data Conversion

|

SQL Server Destination

Are you saying something like:

Flat File

...

I have to ask this question:

In poorly designed tables that have 400+ columns (but luckily do have a unique guid as a PK), wouldn't it just be easier to check...

In the scripts above, there's just that:

@MinPages int = 50, (could be any # of course)

@FragStart int = 10,

@FragEnd int = 25

/* Remove records not needed for the Cursor */

DELETE...

ISNULL may still be preferred as ISNULL will cast the result to the datatype of the first expression evaluated.

Again, just a performance thought - hope it works out either way!

Just wanted to throw this out there: I don't believe you should never set a maximum for the tempdb files (more specifically the LDF files), it's better to let them...

I would reccomend using ISNULL() instead of COALESCE()

SQL Server will most often interpret COALESCE as a CASE expression which can hinder the query optimizer from generating/choosing an optimal query plan...

The issue was due to the fact I have 2 ?'s in my Execute SQL task, while they represent the exact same parameter, I had only created 1 parameter -...

Thanks,

I have changed the Paramter Name to 0 and still receive:

SSIS package "F-Tables.dtsx" starting.

Error: 0xC002F210 at Execute SQL Task, Execute SQL Task: Executing the query "UPDATE _ReadyTables

SET Loaded = 1

WHERE...

But wouldn't that defeat the purpose of getting a date like "2011-04-08 00:00:00.000" in the first place?

SELECT DATEADD(dd,0,GETDATE()) results in "2011-04-08 09:17:05.080"

Consider I have a developer who writes...

I am having a similar issue...but just can't get this too work. Why is SSIS so frustrating? To read about how to do something and then actually trying...

Jeff, what do you suggest as a best-practice for returning a date with 00:00:00.000?

In our existing architecture I don't know if we have much choice with our linked servers. The tables we have from one of the 3rd party DB systems doesn't...

Would there be any performance benefit to disabling the Shared Memory Protocol?

We have a server that executes some rather large queries then pulls the data back to it...

I know this is an old post but wanted to ask if any of you knew which counters should be added to perfmon to monitor a SQL 2008 SP2 Server...

Thanks so much for your assistance on this!

FYI - the server default for MAXDOP is 0 (on all our servers). With MAXDOP, I've always been under the impression that...