Nope, there is no truncation error. A truncation error would be a violation of the input or output column definitions. The truncation is done by the defined data...

What I read in the middle of that page:

If the length of an output column of string data is shorter than the length...

This seems to work:

EXEC sys.sp_serveroption @server = N'currentname', @optname = 'name',

...

This is a generalization that may or may not be useful, but a temp table will not initially have any statistics which might speed up your query. Although SQL...

You may want a script that recreates all the indexes.

WITH ftCat AS (

SELECT CatalogName = QUOTENAME(c.name), is_default, is_accent_sensitivity_on,

...

You can set different policies for different data stores on the same hardware, if your SAN (and/or SAN administrator) is flexible enough. So even though they share hardware with...

The Configuration Wizard has no knowledge of the extra columns in the base table, and the SSIS_Config view it is updating doesn't include the EnvironmentEnum column so anything it inserts...

You might look into the stored procedure that is called and see if it can be modified to handle more than one row at a time. You might be...

I like using WITH XMLNAMESPACES to avoid having "declare namespace DTS=" all over the place. And there are differences in the SSIS XML schema for 2005, 2008, and 2012,...

We use DBAmp, and one of the reasons we chose it was the licensing model. You pay for each SalesForce production instance, not per SQL Server. So we...

I've looked at the new package configuration and deployment features in SQL 2012-2014, and while I wish they were there from the beginning I don't see anything that makes me...

You don't spell out the format of the header record. I assume it is column names, in which case a regular data flow task with a flat file output...

If you're creating the text file in a data flow, the columns are fixed and you won't be able to define a different format for the trailer record (going to...

One criticism would be using "WHERE DATEPART(yyyy,Call_Date)" everywhere. It is much better to set @ArchiveDate to the oldest instant you want to keep (say midnight Jan 1 of the...

I have a colleague who seems to be a big fan of ELTLTTLTTTTL processes. It's just not enterprisey enough if there aren't multiple redundant copies of the data.

I prefer...