It is 2008. Not 1992. Why are we still intentionally creating filenames that conform to the limitations of ancient DOS and Windows 3.1 naming standards? This came up today in one of the SQL Server newsgroups, where a user was trying to find the data file for the Northwind database he was sure had just installed. Why couldn't he find it? Because he was searching for Northwind.mdf. Silly user! It's obviously going to be Northwnd.mdf. You should know that if i follows o, or if there are two e's, then you drop the second and all subsequent vowels to make an 8.3 filename. However, if you have a double o, two e's, or i before e, then you drop the first vowel that appears. *smacks forehead*
If they couldn't call it Northwind.mdf because of the 8.3 limitation, then why didn't they pick a name they could still spell completely? Eastwind and Westwind come to mind. I wonder if I should file a suggestion on Connect to finally name the SQL Server executable correctly? I'm sure there are still people who try to find sqlserver.exe or sqlsrvr.exe or sqlsrver.exe...