New in Sql Server 2019

You recognized this message  ?

String or Binary data would be truncated …

Now find the problem/column/value where this error was raised. It’s like search the needle  in the haystack…

Now, new in sql server 2019 , this message will be replace ( hip hip hurrah!) with a new message:

String or binary data would be truncated in table ‘DatabaseName.SchemaName.TableName’, column ‘ColumnName’. Truncated value: ‘xxxYYYzzz’

 

Will be available, also, in :

• Sql server 2017 + CU12
• SQL Server 2016 SP2 CU

but not as default. (To activate it, in this versions, you need to use trace flag 460).

For the moment, in sql server 2019, you still need TF 460 to activate, but in the next release of sql server 2019, it will be activated as default.

 

Enough with message ID 8152 , the new message ID is 2628.

 

I’m very happy on this new feature.

 

S

 

 

 

ORM

Recently , I started to be involve in a Dynamic AX project.
For the moment, I discovered the following:

– Dynamic AX is not using the full power of sql server;
– sql server it is used only for storing; for storing , you can use a
spreed sheet from excel…
– is not a OLTP , more like a OLAP
– normalization ? what is this ?
– Reference integrity ? Trusted relations ? what are these ?

Before this, it was an internally developed ERP , that was doing the job. The final user was a little grumble, because they always throw stuff on developer , because they were inside company. After the new implementation, nothing was working, even now, after 3 years, are problems, speed is only slow and super slow. Now they say : “what good was previous ERP…”

I don’t know  on what , management made the deci$$$ion to implement that solution, but definitely they took a wrong decision and they don’t have the power to admit   …

S