« first day (3564 days earlier)      last day (1322 days later) » 

12:55 AM
No active COVID-19 community cases in New Zealand now. The last of the recent outbreak have recovered. The only people with COVID-19 in New Zealand now are in secure quarantine having flown in with it.
 
 
2 hours later…
2:45 AM
And boy, were their arms tired!
 
 
2 hours later…
5:07 AM
Seems like these moderator elections will follow the general us election trend
 
 
2 hours later…
6:55 AM
Morning
 
7:21 AM
@PaulWhite ... the only people known with COVID-19 ...
 
7:39 AM
Mornin
g
 
8:29 AM
Morning all. All of Ireland (26 counties) in stage 3 restrictions! Many experts see us in stage 4 or even 5 by Christmas...
 
Same crap here, we don't have predefined stages but we tightened the restrictions as well yesterday
I'm not sure our government is handling it well "you can only invite 4 people instead of 5 starting tomorrow" ,I'm not sure that will change a whole lot, and the people not counting still won't be counting
I get the impression it's pretty mucha guessing game because "we have to do something"
 
Nobody has a clear idea about what to do. Same recipe everywhere.
 
plus Trump proved there is no reason to worry, right
 
9:13 AM
@ypercubeᵀᴹ Yes that's true. However, the last case was 25 September and there has been widespread testing since. If I recall correctly we passed 95% confidence of elimination some days ago. No guarantees of course.
 
ah good
I was more of making a joke - of myself.
JEAGL
Like the 3 scientists that travel on a foreign country and notice some black sheep on a nearby hill.
The biologist says: oh the sheep are black in this country
The physicist corrects him: no, the sheep on this hill are black
and the mathematician: no, these 17 sheep are black on the side we can see
3
 
9:28 AM
very good JEAGL!
 
 
2 hours later…
11:34 AM
I wonder how MS LocalDb treats IDENTITY columns.
It seems it's adding 10000 every time you open a connection
 
@TomV For us it's a maximum of 6 in a house/dwelling from a maximum of 2 households!
 
11:58 AM
@McNets did you restart in the mean time?
 
@ypercubeᵀᴹ It's a localdb that I use in Visual Studio to make some tests, yes I've restarted my laptop some times.
 
6
Q: Identity value jumps when restarting SQL Server

Alok Chandra ShahiWe just switched from SQL Server 2008 R2 to SQL Server 2012. I am facing a problem with identity columns: Whenever I restart SQL Server, the seed value for each identity column is increased by 1000 (for int identity columns it is 1000 and for bigint it is 10,000). For example, if the next int id...

not sure if localdb is different and uses 10000 instead of 1000 or you restarted 10 times ;)
> To improve efficiency, SQL Server 2012 (and later) logs only the allocation of a batch of identity values. The allocated range is cached and issued on demand until a new batch of values is needed.

If SQL Server is restarted without the database containing the identity object being checkpointed on shut down, any remaining unused values in the cached range are lost, resulting in a jump in the values on restart.
 
@ypercubeᵀᴹ It's not a real issue, production db is running on Azure, but it's weird though
 
 
2 hours later…
1:51 PM
Morning
 
2:50 PM
-2
Q: Why is MongoDB losing in this comparison benchmark?

user1034912MongoDB is known to be super fast... at least that's what people say... though in this benchmark, RDBMS esspecially Postgres dominates. https://www.techempower.com/benchmarks/ This is very reliable benchmark as they create tests in a common-environment.

 
@ypercubeᵀᴹ might be a bigint identity?
 
@PaulWhite yes
 
3:06 PM
you can turn caching off, not sure if it is functional in localdb though
ALTER DATABASE SCOPED CONFIGURATION ... IDENTITY_CACHE
IDENTITY_CACHE = { ON | OFF }

APPLIES TO: SQL Server (Starting with SQL Server 2017 (14.x)) and Azure SQL Database

Enables or disables identity cache at the database level. The default is ON. Identity caching is used to improve INSERT performance on tables with identity columns. To avoid gaps in the values of an identity column in cases where the server restarts unexpectedly or fails over to a secondary server, disable the IDENTITY_CACHE option. This option is similar to the existing Trace Flag 272, except that it can be set at the database level rather than only at the server level.
 
@PaulWhite thank you.
 
3:44 PM
@ypercubeᵀᴹ who wants to tell them?
 
4:22 PM
bit awkward
 

« first day (3564 days earlier)      last day (1322 days later) »