358 reputation
115
bio website
location Toronto, Canada
age
visits member for 2 years, 10 months
seen Jul 17 at 17:53

SQL Server 2005/2008/2012


May
14
comment Missing or lost transaction and no errors to show what went wrong
Similar issue I have found: dbforums.com/microsoft-sql-server/… - I wonder how to find this Rollback transaction to get the data that was lost.
May
14
asked Missing or lost transaction and no errors to show what went wrong
May
9
revised SQL Server Browser uses NT AUTHORITY\SYSTEM account and logon failure error in SQL Log
edited body
May
9
asked SQL Server Browser uses NT AUTHORITY\SYSTEM account and logon failure error in SQL Log
Apr
24
accepted Cannot remove Mirroring / nor restore or delete database:Error 3456 (SQL Server 2012)
Jan
23
comment Cannot remove Mirroring / nor restore or delete database:Error 3456 (SQL Server 2012)
Will do thanks! This was a virtual machine that I shut down, FYI
Jan
22
comment Cannot remove Mirroring / nor restore or delete database:Error 3456 (SQL Server 2012)
Also Remus, this is why I could not update the database.
Jan
22
answered Cannot remove Mirroring / nor restore or delete database:Error 3456 (SQL Server 2012)
Jan
22
comment Cannot remove Mirroring / nor restore or delete database:Error 3456 (SQL Server 2012)
Yes this is what I had to do. Luckily the Primary was not corrupted. The mirroring is Asynchronous so - well I am still confused why the corruption happened in the first place!
Jan
21
comment Cannot remove Mirroring / nor restore or delete database:Error 3456 (SQL Server 2012)
Nothing at all coming up under all Broker events for Mirror and for Principal.
Jan
21
comment Cannot remove Mirroring / nor restore or delete database:Error 3456 (SQL Server 2012)
Cool! I will try it, but note, I already disabled Mirroring for this database on the Principal. So it should not be showing errors on Principal. It's the Mirror Database that got stuck with error and is not accepting any kind of changes including ALTER SET PARTNER OFF.
Jan
21
comment Cannot remove Mirroring / nor restore or delete database:Error 3456 (SQL Server 2012)
Because there is a live database on Principal - I worry this is not a good approach. I definitely do not want it to corrupt the other database. I really just want to drop this corrupted one... :) My plan right now is to shut down the Mirror SQL Service and rename the MDF/LDF files & basically steal them from under its nose. I hope that doesn't corrupt the SQL Server instance itself.
Jan
21
comment Cannot remove Mirroring / nor restore or delete database:Error 3456 (SQL Server 2012)
Hi mrdenny, for a period of short time the Mirror could not reach the Principal (I had to shut it down to physically change LAN connection but the LAN had no connectivity when I restarted the machine and this is when this happened). Right now it can reach the Principal and there are multiple databases with this Principal that are working fine with mirroring. Just this one database was not able to resume mirroring. If I run this - will it disrupt the other databases? Thanks!
Jan
21
revised Cannot remove Mirroring / nor restore or delete database:Error 3456 (SQL Server 2012)
added 573 characters in body
Jan
20
asked Cannot remove Mirroring / nor restore or delete database:Error 3456 (SQL Server 2012)
Jan
7
awarded  Critic
Jan
7
comment Moving rows from one table to another
Yes, that is what I meant. Thanks, I see your point.
Jan
4
accepted Moving rows from one table to another
Jan
4
comment Moving rows from one table to another
None of the above. I suppose I could go that route, I like code minimalism. I just do not want to lose records if the insert fails for any reason. (ie: table locking, timeouts, etc) Thank you!
Jan
4
asked Moving rows from one table to another