SSDT will install with a visual studio shell - no need to get a full version of visual studio just for this.

The following may help if the truncation error is on the load to the final table - http://www.sqlservercentral.com/Forums/Topic1300952-364-1.aspx

if the error is on the input file itself then changing...

as I am also a Oracle/DB2 person I have used these a lot in production - and the current projects I am working on 2014 will use them also.

...

different collation between instance, tempdb and other databases is not a problem but it does require that the code is aware of it and deals with it.

Not doing the code...

try

if object_id('sp_GetDiskSpaceStats') is not null

drop procedure dbo.sp_GetDiskSpaceStats;

go

create procedure dbo.sp_GetDiskSpaceStats

as

begin

set nocount on;

if object_id('tempdb..#tmpFileList') is not null

...

time to put more memory on that machine.

there can be several reasons for that low value to show up now

- more data on tables

- bad sqls processing lots of...

and you may also consider moving to the a runtime

2013 - https://www.microsoft.com/en-us/download/details.aspx?id=39358

2016 - https://www.microsoft.com/en-US/download/details.aspx?id=50040

register ,go to downloads, search for "sql server" and both versions appear

and try this link - may or not work https://myprodscussu1.app.vssubscriptions.visualstudio.com/Downloads?q=sql%20server

sorry but yes - it is still available there to download - you do need to register (free) for web essentials and it is then available

I think you can download both from dev essentials - https://www.visualstudio.com/en-us/products/visual-studio-dev-essentials-vs.aspx

two possibilities

1 - package runs with a config file or /set parameters that enable those steps when running on sql server - this may either be from the dtexec command...

restore needs to be done using option keep_cdc.

you now either need to do the restore again and apply any new transaction to that db if required or you can enable...

Interpretation on one my my clients, a major enterprise, is that as soon as the data is restored to a non prod environment it is no longer production data. And...

that is the reason why whenever looking at this type of data I use a replace(field, char(0), ' ') to look at the contents - in addition to the convert(varbinary...0...

j-1064772 (6/21/2016)

---

[h3]select convert(varchar(max), val) as NormalConvert -- gets obliterated as second byte is NULL[/h3]

"Obliterated" ?

Isn't the 00 byte a terminator as in other languages ? So the conversion simply stops...