Error 5009 Sql Server
Contents |
(Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeLibraryLearnDownloadsForums Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: Msg 5009 Trying to remove a log file from a SQL Server 2008R2 database SQL Server > SQL Server Manageability Question
Error 5009 Sophos
0 Sign in to vote I have a database with a Primary File Group error 5009 0x8000ffff and Secondary File Group that is set as the default. There are also 2 log files. I am trying to delete sql server one or more files listed in the statement could not be found or could not be initialized one of the log files and it neither allows me to shrink it or delete it (returns: Msg 5009, Level 16, State 9, Line 1 One or more files listed in the statement could not be found or could not be initialized.) for either event. I have read http://support.microsoft.com/kb/2673247 and http://connect.microsoft.com/SQLServer/feedback/details/482820/orphaned-log-file-can-not-delete-log-file-sysfiles1-duplicate-namesnd 259164 (Denali). Both related to the same problem of creating a file and mistakenly giving it the wrong data type. This is not the case here. The database has been operating correctly sincne an update from 2005 to 2008 R2 in November of 2011 (when we rebuilt our virtual database servers from the ground up). We are starting to get some performance issues with this database (as well as space constraints until we upgrade to SQL Server 2012 this year) so I attempted a shrink file. This is where I encountered the 5009 error first (and the first time I've gotten that particular error). I am not sure if I follow the same procedures or not in the listed KB article. Cansomeone please advise? Thank you for your assistance. Friday, March 08, 2013 8:00 PM Reply | Quote Answers 1 Sign in to vote Hi If you want to delete log file, first you have to clear it using option empty file. Database Engine no longer allows data to be placed on the file after the shrink operation with EMPTYFILE option, the empty file can be removed by using the ALTER DATABASE statement or SQL Server Management Studio. DBCC SHRINKFILE (Testlog, EMPTYFILE); if you still face issue , please run select name , log_reuse_wait_desc from sys.databases where name = dbname log_reuse_wait_desc will tell you what is stopping logfile shrinking Thanks Saurabh Sinha http://saurabhsinhainblogs.blogspot.in/ Please click the Mark as answer button and vote as helpful if this reply solves your problem Edited by Saurabh Sinha DBA Monday, March 11, 2013 1:20 PM Proposed as
Recent PostsRecent Posts Popular TopicsPopular Topics Home Search Members Calendar Who's On Home » SQL Server 2008 » SQL Server 2008 Administration » Transaction Log File "Does not Exist" - Help,... 40 posts,Page 1 of 41234»»» Transaction Log File "Does not Exist" - Help, please Rate Topic Display Mode Topic Options Author Message Brandie TarvinBrandie Tarvin Posted Thursday, October 20, 2011 6:03 AM SSCertifiable Group: General Forum Members Last Login: 2 days ago @ 9:30 https://social.msdn.microsoft.com/Forums/silverlight/en-US/81d18a77-cb39-4147-a2b0-555bcbc5944d/msg-5009-trying-to-remove-a-log-file-from-a-sql-server-2008r2-database?forum=sqlkjmanageability AM Points: 7,366, Visits: 8,517 I'm having problems with modify the settings on a secondary transaction log file in SSMS, so I thought I'd try with T-SQL. Turns out no matter what method I use, SQL doesn't think the secondary log file exists, but it lists it in a "Select * from sysfiles" command and in the GUI. I'm really http://www.sqlservercentral.com/Forums/Topic1193581-1550-1.aspx confused here.We're in the middle of rolling out SP2 (it hit the Dev environment, but not Production yet). Here's what I'm running:Production: Microsoft SQL Server 2008 (SP1) - 10.0.2531.0 (X64) Mar 29 2009 10:11:52 Copyright (c) 1988-2008 Microsoft Corporation Enterprise Edition (64-bit) on Windows NT 6.0
not be found or could not be initialized. Severity level:16. Description:This error message appears when you try to use a file in a statement, however this file couldn't not be found or initialized Consequences:The T-SQL statement can http://www.sql-server-performance.com/2007/file-could-not-be-found-or-initialized/ be parsed, but causes the error at runtime. Resolution:Errors of the Severity Level 16 are generated by the user and can be fixed by the SQL Server user. The statement cannot be executed this way. This error can have http://stackoverflow.com/questions/1341395/file-system-not-supported-error-while-adding-a-file-to-sql-filegroup-with-filest multiple root causes. Versions:All versions of SQL Server. Example(s):ALTER DATABASE MyExample ADD FILE ( NAME = Test1dat2, FILENAME = ‘abc.ndf', SIZE = 5MB, MAXSIZE = 10MB, FILEGROWTH = 50MB ); Remarks:In the above example we try to add a error 5009 file named abc.ndf to the MyExample database. Because the ndf extension is used for non-primary database files, the error 5105 is raised. In the further course of the statement can the file not be found, and the error 5009 is raised. ASK A QUESTION Tweet Array Errors No comments yet... Be the first to leave a reply! Leave a Reply Click here to cancel reply. Popular Latest Tags Setting up Transactional Replication in SQL Server 2008 R2. November 30, error 5009 sql -0001 Backing Up a SQL Server Database Directly Onto a Remote Server November 30, -0001 Recovering a SQL Server Database from Suspect Mode November 30, -0001 SQL Server T-SQL Tuning - NOT IN and NOT Exists November 30, -0001 SQL Server T-SQL Tuning - Temp Tables, Table Variables and Union November 30, -0001 SQL Server Logical Reads – What do they really tell us? October 4, 2016 Physical Join Operators in SQL Server - Hash Operator September 21, 2016 Physical Join Operators in SQL Server - Merge Operator August 25, 2016 Techniques to Monitor SQL Server memory usage August 12, 2016 Recovering a SQL Server Database from Suspect Mode August 7, 2016 Forum posts... 2008 R2 2012 Agent AlwaysOn Analysis Services Backup Clustering Data Mining deadlock Denormalization Disaster Recovery Email Entity Framework Excel Geo high availability Identity Identity Column index Jobs Log Shipping mail Monitoring Oracle Query Query Plan range Replication Reporting Services Report Manager Restore Security Spatial Data SSIS SSMS SSRS Stored Procedures T-SQL task Temp Table Transactional Replication transactions TSQL Tuning UNION CONTACT SQL-SERVER-PERFORMANCE.COM © 2016 SQL Server Performance. All Rights Reserved 4281 Express Lane, Suite L7710, Sarasota, FL 34238, Software Reviews | Book Reviews | FAQs | Tips | Articles | Performance Tuning | Audit | BI | Clustering | Developer | Reporting | DBA | ASP.NET Ado | Views tips | | Developer FAQs | Replication Tips | OS Tips
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up file system not supported error while adding a file to sql filegroup with filestream up vote 1 down vote favorite hi i am a beginner with sql server 2008, i was trying to add a file to a filegroup so that i an create a table which uses filestream, but i keep getting an errors. here is the code that i am trying: ALTER DATABASE dbtry1 ADD FILEGROUP dbtry1_fg_filestream CONTAINS FILESTREAM GO ALTER DATABASE dbtry1 ADD FILE ( NAME= 'dbtry1_filestream', FILENAME = 'E:\Projects\fs.ndf' ) TO FILEGROUP dbtry1_fg_filestream GO the errors: Msg 5134, Level 16, State 2, Line 1 The path that is specified by 'E:\Projects\fs.ndf' cannot be used for FILESTREAM files because it is not on a supported file system. Msg 5009, Level 16, State 14, Line 1 One or more files listed in the statement could not be found or could not be initialized. Please help! sql tsql sql-server-2008 filestream filegroup share|improve this question edited Jan 5 '10 at 20:26 gbn 267k40374480 asked Aug 27 '09 at 14:13 Sneha 61214 add a comment| 1 Answer 1 active oldest votes up vote 0 down vote it is not on a supported file system. Is it local NTFS? Compressed and not using 4k clusters? More info here Edit: After comment.. no, you can't use FAT 32. Why do you still have this? You are limited to 4GB file