In the table definition, I saw:
Latitude -> varchar(50) Longitude -> nvarchar(50)
Immediately, obviously, I asked what was behind it: - it is positive that these values are actually numerical in nature. In short: I postulated that they will be numerical, decimal in fact, and we will reject the philosophy of “thinking in lines.”
Now, for the horns of my dilemma, I simply went ahead and typed:
Latitude -> decimal(2, 4)
But hold on a second, 4 is wrong, isn't it? Correctly. Therefore, I thought that before the threshold, before I realize (per second, perhaps add) that 6 or 8 , perhaps, will not reduce it either. So first, first ...
Do I really insist that we do this? And if so ...
What precision should be stored to ensure that we can store all the value that needs to be inserted? For example, is there any predefined specification?
I don't just want to use something like Latitude -> decimal(2, 16) just to make it as erroneous as decimal(2, 2) in principle. And a similar question arises specifically for Longitude, but I assume that the answer to one will be sufficient for the other, i.e. decimal(3, answer) .
We are using MSSQL Server 2005.
It seems I am educating myself with SQL Server from manual experience and therefore do not make parts of this question irrelevant: I can use decimal(x, max(x)) not decimal(x, y) anyway! Leave the question as is for input.