131–140 of 146 posts
Earlier quoted context omitted.
It's actually fairly common to see this problem crop up in systems that are using a database table as a queue (which is a bad idea for many reasons, but people still do it) in which case the number of live rows in the table can be fairly small.
If a SQLServer instance is killed unceremoniously it adds 1000 to the pk increment.
Earlier quoted context omitted.
Cheap solution, sure, add an index. But you're asking an OLAP question question of an OLTP system. Questions like that are best asked at least of an out-of-production read replica or better an analytics db.
I don't really understand this - what is an out of production read replica? Why wouldn't it just go to a production read replica? And what is an "analytics db" in this context?
Earlier quoted context omitted.
What if you wanted to select "top 100 most expensive products" or number of products between $0.01 and $10, $10.01 and $100, $100.01 and $1000? Sure you could do a full table scan on your products table on both queries but an index on price would speed both queries up a lot if you have a lot of products. Of course you have to determine if the index would be used enough to make up for the extra time on index update wh…
Cheap solution, sure, add an index. But you're asking an OLAP question question of an OLTP system. Questions like that are best asked at least of an out-of-production read replica or better an analytics db.
Earlier quoted context omitted.
If a SQLServer instance is killed unceremoniously it adds 1000 to the pk increment.
I'm trying not to imagine the poor SQL Server that has crashed one or two million times and hence pushed the ID values into the billions!
Reminds me of the 100 millionth OpenStreetMap changeset (commit). A few people, myself included, were casually trying for it but in the end it went to someone who wasn't trying and just busy mapping Africa! Much more wholesome, seeing it with hindsight. This person was also previously nominated for an OSM award. I guess it helps that openstreetmap doesn't really allow for creating crap, because it's all live in produ…
A friend of mine spent an entire workday figuring out how to ensure he created the millionth ticket in our help desk. Not sure how he cracked it in the end but we had a little team party to celebrate the achievement. This was probably fifteen years ago. I feel like working in tech was more fun back then.
We were being onboarded, they were just for demo and were promptly deleted. No one cared about the Cool Numbers.
Earlier quoted context omitted.
A friend of mine spent an entire workday figuring out how to ensure he created the millionth ticket in our help desk. Not sure how he cracked it in the end but we had a little team party to celebrate the achievement. This was probably fifteen years ago. I feel like working in tech was more fun back then.
I was involved in the 99,999th and the 100,000th one in my FQA days. We were being onboarded, they were just for demo and were promptly deleted. No one cared about the Cool Numbers.
The repo seems to have gotten renamed and now redirects to https://github.com/AasishPokhrel/repository/ Lame. :-(
Earlier quoted context omitted.
The rate of creation is like meh, but being able to enumerate all of the repos might be problematic, following new repos and scanning them for leaked credentials could be a negative... but github may have a feed of new repos anyway? Also, having a sequence implies at least a global lock on that sequence during repo creation. Repo creation could otherwise be a scoped lock. OTOH, it's not necessarily handled that way -…
> but github may have a feed of new repos anyway? Yes: https://docs.github.com/en/rest/repos/repos?apiVersion=2022-... (you can filter to only show repositories created since a given date).
they have some secret leaking infra for enterprise
Earlier quoted context omitted.
Changing the type of the column is no big deal per se, except on a massive table it’s a non-trivial operation, BUT you also have to change the type in everything that touches it, everywhere it’s assigned or copied, everywhere it’s sent over the wire and deserialized where assumptions might be made, any tests, and on, and on. And god help you if you’ve got stuff like int.MaxValue having a special meaning (we didn’t in…
Well done. Unsung heroes keeping it all going, and unsung villains who chose int32 in the first place long gone :-)