In my SQL Server database, I have a column designated for storing numeric data, but the values it holds can vary significantly. For instance, I might have numbers in the billions, or values as small as 1.355 E -16. I’m considering setting the numeric type to a large range, such as numeric(35,20), but I’m concerned this would inefficiently occupy a lot of space in my database. Is there an efficient approach to manage these numeric values similar to how varchar handles strings of different lengths?
hey, liam, can’t it be useful to consider using float or double types for precision and range if you don’t need exact decimals? it mght be more space-efficient. what trade-offs are you weighing between space and precision? curious if anyone has tackled similar challenges with sql? 