June 10, 2008 at 11:23 am
I have installed a named instance of SQL Server 2005 for use with Project Server 2007. Per company policy, I have installed the server instance and system databases on the smaller C: drive of the machine, where the operating system also resides. I set the default location for new database files (.mdf and .log files) to the larger D: drive.
After this, I installed Project Server 2007 on a separate machine, and configured it to use the SQL Server 2005 named instance I described above for content databases. I expected the content database files to be created on the D: drive, but instead it automatically plops Project content databases in the root directory, on the C: drive. There is just not enough space to handle Project content on C:!
Is there a way to change Project Server's configuration to put database files on the D: drive? Or, do I have to uninstall the entire instance of SQL Server, just to install it again with the root directory on the D: drive?
If I detach Project Server databases, move them, and reattach them, it might work, if I can successfully stop the Project services so they will disconnect from the databases. However, I will have to do this manual process again and again for every new Project Server database!
What do I do?
June 10, 2008 at 12:17 pm
I don't know about settings in Project Server. There probably is one, but I don't know where to even start.
I do know you could set up an automatic job to move database files to the D drive, from C drive. Not sure how that would affect Project Server though.
Have you tried digging through the documentation with Project Server to see if there's an Options menu that allows you to control default database locations?
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
June 10, 2008 at 1:34 pm
During the initial configuration, the only configuration options given were 1) the database server or instance, and 2) the service account chosen to communicate with the database server.
Also, when I go to Project Server Central Administration site, Operations, Default Database Server, and view the configuration, it still only gives those 2 variables.
I am not as familiar with Project as with SQL Server, but I would think that Project Server would follow the default path for user databases that I set in SQL Server, but I guess it follows the root directory instead. Someone must have run into this problem before me.
I'm wondering, is this really unconfigurable? Do I really have to uninstall the entire instance of SQL Server and re-install it, apply all service packs, and possibly even uninstall and re-install Project server too?
June 10, 2008 at 2:09 pm
And, even if you do all that unistalling and re-installing, will that actually do anything, or will Project Server still insist on creating databases on C drive of the SQL server? That's another possibility.
If you don't get an answer from someone who knows more than I do on this relatively soon, might be time to fire off a tech support request to MS.
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply