May
24
comment Asynchronous availability groups not synchronizing on SQL Server on Ubuntu
I may be wrong in the "state" I expect... but I inserted 1 row on a sleeping server on may 22nd. It is still not replicated on the secondary (The DB is read only accessible so I simply run the same select on both node). When set to sync, it does replicate live without any delay...
May
23
awarded  Curious
May
22
asked Asynchronous availability groups not synchronizing on SQL Server on Ubuntu
Jan
18
answered Load balancing Availability groups with SQL Server Standard
2018
Dec
12
comment Correct way to group by month and year?
On a performance point of view, wouldn't that group by using Windows function forces a full scan ? If it's a big table and if there is some where clauses that return only a small part of the data, I would look for a computed column on year and one on month (persistent column).
Dec
12
answered SQL Server - How to copy database daily
Dec
12
comment Why is my DR AG database in the “recovery pending” state?
You would normally have a fileshare ressource in your cluster to avoid Quorum problem. How many node will you have ? It's frequent to have 3 nodes for that kind of setup. 2 node in the same site in "synchronous" mode (this will have automatic failover and will provide HA) 1 node in another site in "Asynchronous" mode (this one will not have automatic failover and will be there for DR (with some possible data loss).
Dec
12
answered Creating/restoring mdf/ldf to non-default file location giving access denied
Nov
30
revised Availability Group being PARTIALLY_HEALTHY
added 316 characters in body
Nov
29
comment Availability Group being PARTIALLY_HEALTHY
Well, there is a lot of columns in this DMV, the syncronization_state_desc was "SYNCHRONIZING" and the synchronization_health_desc was "PARTIALLY_HEALTHY"
Nov
23
asked Availability Group being PARTIALLY_HEALTHY
Jan
5
answered What is the best way to know the structure of a database
Jan
5
comment A query to find patients with any 4 visits within a 365 day period
Just change the "a.AdmitDateTime >= '2016'" by something like : a.AdmitDateTime > Dateadd(day,-365, getdate())
Jan
3
awarded  Yearling
Jan
3
revised A query to find patients with any 4 visits within a 365 day period
deleted 35 characters in body
Jan
3
answered A query to find patients with any 4 visits within a 365 day period
Jan
3
revised Multiple Batches in SQL Server Migration Script
added 381 characters in body
Jan
3
answered Multiple Batches in SQL Server Migration Script
Jan
3
comment Getting error running DBCC Checktable(tablename, repair_allow_data_loss)
"Index row in index 'nc1' (ID 2) does not match any data row". The value in that non-clustered index is not found in the clustered index... If that row is corrupted in the cluster index, that would explain why it's not found. Deleting the corrupted row from the clustered index and recreating it with the value from that non-clustered index may be a way to recover it without data lost.
Jan
3
comment Getting error running DBCC Checktable(tablename, repair_allow_data_loss)
index ID 1... I guess that it's the cluster index that is corrupt. If you have non cluster index with all the other column included, you may be able to recover that row from the non-clustered indexes.