|
|
|
SSC Veteran
      
Group: General Forum Members
Last Login: Wednesday, April 17, 2013 10:44 AM
Points: 209,
Visits: 655
|
|
The production database has 1 MDF and 1 log file.
The log file extension is idf instead of LDF. Would this cause issues?
|
|
|
|
|
SSC Eights!
      
Group: General Forum Members
Last Login: 2 days ago @ 10:16 AM
Points: 863,
Visits: 2,135
|
|
i havent heard of it, is the database accessible for you?
can you check the extension again?
Regards Durai Nagarajan
|
|
|
|
|
SSC-Dedicated
           
Group: General Forum Members
Last Login: Today @ 4:08 PM
Points: 38,099,
Visits: 30,392
|
|
You could call the transaction log file readme.txt if you wanted. SQL doesn't care what the name or extension of the file is in any way.
Gail Shaw Microsoft Certified Master: SQL Server 2008, MVP SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
We walk in the dark places no others will enter We stand on the bridge and no one may pass
|
|
|
|
|
SSC Veteran
      
Group: General Forum Members
Last Login: Wednesday, April 17, 2013 10:44 AM
Points: 209,
Visits: 655
|
|
Interesting. I did not realize that. I am still going to relocate if off the data drive tonight and move it over to a dedicated log drive.
Thanks again Gail!
|
|
|
|
|
SSC-Addicted
      
Group: General Forum Members
Last Login: Monday, June 10, 2013 10:06 PM
Points: 442,
Visits: 1,304
|
|
Using MDF, NDF & LDF is really historical and convention more than anything else, it does however allow the files to be easily identified as database files. When you move the log file to the log drive you can rename the physical file, including the file extension(s) as shown below.
ALTER DATABASE MyDatabase SET OFFLINE; GO
-- for mdf ALTER DATABASE MyDatabase MODIFY FILE (NAME='MyDatabase', FILENAME='H:\Data\MSSQL.3\MSSQL\Data\MyDatabase.mdf'); GO
-- for ldf ALTER DATABASE MyDatabase MODIFY FILE (NAME='MyDatabase_Log', FILENAME='H:\Data\MSSQL.3\MSSQL\Data\MyDatabase_log.ldf'); GO
-- Move and rename the physical files before the next step as appropriate
ALTER DATABASE MyDatabase SET ONLINE; GO
Cheers
Leo
|
|
|
|
|
Mr or Mrs. 500
      
Group: General Forum Members
Last Login: Today @ 7:36 AM
Points: 533,
Visits: 788
|
|
I can't help myself - I have to ask:
Maybe it could be a lower-case "L" ("l") instead of an Upper-case "I" ?
Regards, Mike
|
|
|
|
|
SSCertifiable
       
Group: General Forum Members
Last Login: Today @ 10:11 AM
Points: 5,242,
Visits: 11,262
|
|
Vertigo44 (2/26/2013) The production database has 1 MDF and 1 log file.
The log file extension is idf instead of LDF. Would this cause issues? You just need to change the name in the SQL Server system catalogs and rename the OS file. Leo has detailed fully for you, you only need to complete the file rename and alter if you just want to rename the file. See my article at this link for more info.
GilaMonster (2/26/2013) You could call the transaction log file readme.txt if you wanted I bet someone, somewhere in the world has too 
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs"
|
|
|
|
|
SSC-Dedicated
           
Group: General Forum Members
Last Login: Today @ 4:08 PM
Points: 38,099,
Visits: 30,392
|
|
Perry Whittle (2/27/2013)
GilaMonster (2/26/2013) You could call the transaction log file readme.txt if you wantedI bet someone, somewhere in the world has too 
For the sake of playing around, I once created a DB where both the data and log files were alternate streams of a text file. Was silly, but it worked. CheckDB wouldn't run on it though.
Gail Shaw Microsoft Certified Master: SQL Server 2008, MVP SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
We walk in the dark places no others will enter We stand on the bridge and no one may pass
|
|
|
|
|
Ten Centuries
      
Group: General Forum Members
Last Login: Wednesday, June 12, 2013 7:02 AM
Points: 1,286,
Visits: 1,411
|
|
As noted previously, SQL itself doesn't care. What does sometimes care is antivirus (not to start a thread on good idea or not, just that some shops do run AV and should be aware of this). They can ignore certain file types by extension (either out or the box or by configuration), and it wouldn't know that IDF is a special file to ignore. That file gets scanned and activity to that file gets scanned. It's a non-obvious performance hit.
I can't comment on all AV packages, but I've had some in the past that would have created a problem with IDF.
|
|
|
|
|
SSC Veteran
      
Group: General Forum Members
Last Login: Wednesday, April 17, 2013 10:44 AM
Points: 209,
Visits: 655
|
|
Tony++ (3/27/2013) As noted previously, SQL itself doesn't care. What does sometimes care is antivirus (not to start a thread on good idea or not, just that some shops do run AV and should be aware of this). They can ignore certain file types by extension (either out or the box or by configuration), and it wouldn't know that IDF is a special file to ignore. That file gets scanned and activity to that file gets scanned. It's a non-obvious performance hit.
I can't comment on all AV packages, but I've had some in the past that would have created a problem with IDF.
This is a good point. That file extension wouldnt be on the exclusions list.
|
|
|
|