I have a sales table where the SalesNo was a happy int. for years. Then I thought I would like to support split transactions. In this instance the salesNo should be 123.1 and 123.2 for example for a split transaction.
So I converted the SQL int to a decimal (16.1) and away we go after some coding. However, SQL Server insists on "appending" a .0 for SaleNo's that are just 123 storing it as 123.0. That causes issues I would rather not code around.
Can I make SQL Server not behave this way?