Re: OT: SQL Server Emergency
On Wednesday 19 July 2006 23:07, Jeff D. Chastain wrote: > in the past that by removing the log file SQL server would rebuild a new > one and you would only loose whatever transactions were in the log file. Well, unless it was half way through doing something, I suppose it might. Doesn't strike me as a very good plan except if-all-else-fails. I don't suppose undeleting the log works ? -- Tom Chiverton This email is sent for and on behalf of Halliwells LLP. Halliwells LLP is a limited liability partnership registered in England and Wales under registered number OC307980 whose registered office address is at St James's Court Brown Street Manchester M2 2JF. A list of members is available for inspection at the registered office. Any reference to a partner in relation to Halliwells LLP means a member of Halliwells LLP. Regulated by the Law Society. CONFIDENTIALITY This email is intended only for the use of the addressee named above and may be confidential or legally privileged. If you are not the addressee you must not read it and must not use any information contained in nor copy it nor inform any person other than Halliwells LLP or the addressee of its existence or contents. If you have received this email in error please delete it and notify Halliwells LLP IT Department on 0870 365 8008. For more information about Halliwells LLP visit www.halliwells.com. ~| Introducing the Fusion Authority Quarterly Update. 80 pages of hard-hitting, up-to-date ColdFusion information by your peers, delivered to your door four times a year. http://www.fusionauthority.com/quarterly Archive: http://www.houseoffusion.com/cf_lists/message.cfm/forumid:4/messageid:247162 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
re: OT: SQL Server Emergency
Okay, I can't detach the database because it is being used in replication. So, I tried to use the stored procedure sp_removedbreplication to stop the replication and I get an error because the database is in recovery/emergency mode. Next Thanks. Sorry for the priority off-topic, but I have a SQL server down and I am running out of ideas. The log file for one of my databases was corrupted. I thought I rememberd in the past that by removing the log file SQL server would rebuild a new one and you would only loose whatever transactions were in the log file. Apparently not. I stopped SQL server, deleted the log file and restarted it. Now the database is marked as suspect. I have tried detaching the database, but the database is/was used in a replication and SQL server won't allow me to detach it. How can I disable the replication in order to detach the database and then reattach it so that it will rebuild a new log file? Thanks. ~| Introducing the Fusion Authority Quarterly Update. 80 pages of hard-hitting, up-to-date ColdFusion information by your peers, delivered to your door four times a year. http://www.fusionauthority.com/quarterly Archive: http://www.houseoffusion.com/cf_lists/message.cfm/forumid:4/messageid:247130 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4