Reputation
453
Top tag
Next privilege 500 Rep.
Access review queues
Badges
6 23
Impact
~34k people reached

  • 0 posts edited
  • 0 helpful flags
  • 44 votes cast
May
14
accepted PostgreSQL + PG_Monz (Zabbix) DB size too large > 1073741824
May
5
awarded  Popular Question
Apr
13
comment Downsides to using SQL 2012 Upgrade as opposed to a fresh install?
I'm just going to post this here (and it's something I'm dealing with as well after having upgraded my version of SQL server instead of doing a fresh install. It's worth a read: dba.stackexchange.com/questions/22402/… (Note speaking of answer by Bijan)
Apr
3
awarded  Popular Question
Mar
18
awarded  Popular Question
Jan
6
awarded  Notable Question
Jan
3
awarded  Yearling
Dec
22
awarded  Popular Question
Dec
20
awarded  Popular Question
Dec
16
awarded  Notable Question
Dec
12
awarded  Popular Question
Nov
17
awarded  Notable Question
Nov
10
awarded  Notable Question
Nov
7
awarded  Popular Question
Oct
28
revised PostgreSQL + PG_Monz (Zabbix) DB size too large > 1073741824
added 182 characters in body
Oct
28
answered PostgreSQL + PG_Monz (Zabbix) DB size too large > 1073741824
Oct
27
asked PostgreSQL + PG_Monz (Zabbix) DB size too large > 1073741824
Sep
24
awarded  Autobiographer
Sep
12
comment Mirroring failed over - created 2 principal database and will not allow me to drop one of them
Yes - at which point the database for which I removed mirroring entered "principal, disonnected" state, this one I attempted to delete and failed. Another database in similar situation (for which I did not try to remove mirroring) reverted to being mirror, synchronized instead.
Sep
12
comment Mirroring failed over - created 2 principal database and will not allow me to drop one of them
Sadly I just solved this problem with a reboot of the server. The databases became Mirror/Synchronized after reboot. Sigh...though I'm glad it's fixed, it's not the solution I was hoping for