SigmundA

6 ms·

31.
by SigmundA 6mo ago
Logically air gapped :) https://docs.aws.amazon.com/aws-backup/latest/devguide/logic...
32.
by SigmundA 6mo ago
Because there is a whole section that describes column based storage without mentioning that some databases have column based storage as an option.
33.
by SigmundA 6mo ago
>Cache locality by default. In a traditional row store, reading all player positions means loading entire rows — names, inventories, health, everything. Most of those bytes are wasted. Not one mention of column stores? This didn't c
34.
by SigmundA 7mo ago
The batteries and phone lines were one system at -48v with power supplies converting AC power to DC while grid / generator is up. The batteries are floated at the line voltage nothing was really charging or discharging and there was no
35.
by SigmundA 7mo ago
Not sure what your point is, I was talking primarily about Class 8 heavy duty commercial trucks (semi) and other medium duty commercial use. All the stuff that makes up emissions gear is highly recyclable and in fact some of it very desirab
36.
by SigmundA 7mo ago
No the DEF systems tend to break down and its mandated the engine go into limp mode when they do, this is hated by those that do not care for emissions and one of the biggest reason to delete by truckers. Also costly to fix the systems out
37.
by SigmundA 7mo ago
There are three main emissions control systems in diesels, the Exhaust Gas Recirculation (EGR), Diesel Particulate Filter (DPF) and Selective Catalytic Reduction (SCR) which uses Diesel Exhaust Fluid (DEF). Any or all can be "deleted&q
38.
by SigmundA 7mo ago
Saw posters on /r/Truckers complaining that truck stops were taking advantage of situation to gouge for DEF too on top of diesel before someone pointed out that Iran is the second largest producer of urea, the primary component of
39.
by SigmundA 7mo ago
There is a lot of space between no acknowledgment at all like this article and tracing down the exact origin of who and when invented to null bit map in what system. Your version comes off as self promotion, going into detail how to impleme
40.
by SigmundA 7mo ago
>You're the one saying a 2 character string is somehow a space savings. If we're going to split hairs that finely then you have to know that any row with a variable length string makes the entire row/index variable length
41.
by SigmundA 7mo ago
Interesting so you don't find it odd that an article about the storage engine of a SQL database system explains the solution to problem without once mentioning that it is the way most other sql database engines solve it? It is mentione
42.
by SigmundA 7mo ago
>Sure they do, because now your row / index is variable length rather than fixed length. Way more complicated. Come on its literally a 2 byte per column header in the row so it just sums the column lengths to get the offset, it does
43.
by SigmundA 7mo ago
https://en.wikipedia.org/wiki/Natural_key you should have learned learn this in your courses. Clam down, I am not suggesting using this for actual domain entity keys, these are used in place of enums and have their adv
44.
by SigmundA 7mo ago
The check is added if it sees a varchar column and nvarchar parameter predicate on it. It currently just does a scan in that situation which orders of magnitude more expensive with a cast for every row vs a single extra cast check on the si
45.
by SigmundA 7mo ago
>Enums are for non user-configurable values In the systems I work with most coded values are user configurable. >But those should have an auto-integer primary key and if you need the description, join for it. Not ergonomic now when qu
46.
by SigmundA 7mo ago
It should not return incorrect results, if the nvarchar only contains ascii it will cast perfectly, if it doesn't then do the slow scan path, it's a simple check and the same work its doing for every row in the current behavior ex
47.
by SigmundA 7mo ago
The non sargeablilty is an optimizer deficiency IMO. It could attempt to cast just like this article is doing manually in code, if that success use index, if it fails scan and cast a million times the other way in a scan.
48.
by SigmundA 7mo ago
We are talking nvarchar here, yes UTF-8 solves this issue completely and MSSQL supports it now days with varchar.
49.
by SigmundA 7mo ago
Mostly agree separate tables can have multiple attributes besides a text description and can be exposed for modification to the application easily so users or administrators can add and modify codes. A common extra attribute for a coded val
50.
by SigmundA 7mo ago
It can run it for a range of values: https://learn.microsoft.com/en-us/sql/relational-databases/p... Also the simpler and maybe better approach is just make the decision every time as an operation in the plan
51.
by SigmundA 7mo ago
How do you store them? Also enums are not user configurable normally. It would be a good feature to have them, but they don't work well in many cases. Typical code tables with code, description and anything else needed for that value w
52.
by SigmundA 7mo ago
UTF-8 was introduced in SQL Server 2019: https://learn.microsoft.com/en-us/sql/sql-server/what-s-new-...
53.
by SigmundA 7mo ago
Specifically not talking about a name field
54.
by SigmundA 7mo ago
I am talking about coded values, like Status = 'A', 'B' or 'C' Taking double the space for this stuff is a waste of resources and nobody usually cares about extended characters here in English language systems
55.
by SigmundA 7mo ago
Can you give an example whats dangerous about converting a nvarchar with only ascii (0-127) then using the index otherwise fallback to a scan? If we simply went to UTF-8 collation using varchar then this wouldn't be an issue either, wh
56.
by SigmundA 7mo ago
Vast majority of text fields I see are coded values that are perfectly fine using ascii, but I deal mostly with English language systems. Text fields that users can type into directly especially multiline tend to need unicode but they are f
57.
by SigmundA 7mo ago
Yes I have run into this regardless of client language and I consider it a defect in the optimizer.
58.
by SigmundA 7mo ago
To complicate matters SQL Server can do Nvarchar compression, but they should have just done UTF-8 long ago: https://learn.microsoft.com/en-us/sql/relational-databases/d... Also UTF-8 is actually just a varch
59.
by SigmundA 7mo ago
UTF-8 is a relatively new thing in MSSQL and had lots of issues initially, I agree it's better and should have been implemented in the product long ago. I have avoided it and have not followed if the issues are fully resolved, I would
60.
by SigmundA 7mo ago
The parameter type is part of the cache identity, nvarchar and varchar would have two cache entries with possibly different plans.

More ›