My biggest XML import job involves 1GB+ files. I never had the nerve to see what happens if you load that much data into an XML variable and try...

In my experience, the inefficiency of flat files comes from my time spent debugging ETL packages when boneheaded third parties don't know how to format them correctly. I just...

A general pattern would be:

SELECT (group by columns), y = MAX(CASE WHEN x THEN y END), z = MAX(CASE WHEN x THEN z END)

GROUP BY (group by columns)

The aggregation function...

If an OPENQUERY statement could make use of the @EndDate parameter, he wouldn't need dynamic SQL in the first place.

I have a lot of code that references our non-SQL accounting...

The syntax error is that the CASE function (not a statement in T-SQL) is missing the END keyword.

A CmdExec job step uses the command interpreter, just like a Command Prompt window or a .bat file. It doesn't do multi-line string literals.

It should work if it's all...

Running a package using the 32-bit version of DTEXEC won't affect any other packages started normally with the 64-bit version.

Unless your package has a "Run Child Package" step that starts...

Are you saying you can't use a view because of the @MaxMinutes variable? You couldn't just hardcode that in the view definition?

How about making it a table-valued function instead...

Your package must use some 32-bit component or driver. Try identify it and find a workaround.

If no workaround can be found, force it to run as 32-bit. You...

The column data types in the flat file source should match the destination table. So the flat file source column should be changed to DT_R4, or the database column...

I don't think #temp will work, it would need to be a global ##temp table. The query is run from a separate connection, so it would not have access...

Hopefully the CRM app rarely does "SELECT * FROM dbo.notes" on the whole table, so doing that in Management Studio is not a useful test. You're just stressing the...

The edition downgrade from Enterprise to Standard is supported for SQL 2014, but I didn't see it listed for SQL 2012. So you may not be able to do...

We run SCOM just fine on Standard Edition. No sense wasting an Enterprise license on it.

Another answer is to set up the Central Management Server in SSMS Registered Servers using an alias. Or go to the existing one and choose "Central Management Server Actions"...