393 reputation
317
bio website
location Toronto, Canada
age
visits member for 3 years, 2 months
seen Nov 10 at 21:44

SQL Server 2005/2008/2012


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
Sep
12
asked Mirroring failed over - created 2 principal database and will not allow me to drop one of them
Aug
28
accepted How to get Identity Column to jump ahead (by say 1000) on SQL Server 2012
Aug
27
asked How to get Identity Column to jump ahead (by say 1000) on SQL Server 2012
Aug
21
accepted PGAdmin III Server Status Error: Could not read directory “pg_log” No such file or directory
Aug
21
revised PGAdmin III Server Status Error: Could not read directory “pg_log” No such file or directory
added 74 characters in body
Aug
21
asked PGAdmin III Server Status Error: Could not read directory “pg_log” No such file or directory
Aug
16
accepted PostgreSQL Slave has more files in pg_xlog than /wal_archive
Aug
15
comment PostgreSQL Slave has more files in pg_xlog than /wal_archive
I think the slave complaining it couldn't find the 00000001000000000000001C file is actually just part of pg_standby as the slave server is not accepting connections and overall infinitely checking for the latest file to be sent to it. I thought this was an error but likely it was not.
Aug
15
comment PostgreSQL Slave has more files in pg_xlog than /wal_archive
@Craig standby.log was never created or at least nowhere to be found. Ultimately, after various attempts to fix situation above because of failures to start the server, I (you may shudder) deleted the /var/lib/postgresql/9.3/main folder contents on the slave (as much as ubuntu would allow me to delete). Performed base backup on the master and rsynced the contents of /var/lib/postgresql/9.3/main over to the slave. I wonder if the large quantity of log files on Standby were just a side effect of streaming replication. I see in your answer you more or less agree that base backup was needed :)
Aug
15
revised PostgreSQL Slave has more files in pg_xlog than /wal_archive
Added more info - directory names and file names
Aug
15
revised PostgreSQL Slave has more files in pg_xlog than /wal_archive
Portion of changes to make the question more complete