Firebird and SQL on same server

[MasterRacker]

DISCLAIMER: Before you tell me I'm nuts (which I already know ;-) ) I don't have the resources to use separate servers.

This is a SQL 2005 server with a mirrored C:, mirrored E: and RAID F:. C: and E: are on 1 SCSI channel and F: is on the other.

My SQL data is on F: and the logs are on E:

So, I have a low volume Firebird based application that I have no other home for. My question is where is the best location for the Firebird data? I'm leaning to the C: drive (I have plenty of available space.) It's the same SCSI channel as the SQL logs but it's at least a different volume.

What are people's thoughts?

_____
Jeff
[small][purple]It's never too early to begin preparing for [/purple]International Talk Like a Pirate Day
"The software I buy sucks, The software I write sucks. It's time to give up and have a beer..." - Me[/small]

 

[macleod1021]

With all SQL datbases, you should put the database files on a raid volume. I would recommend getting another raid drive for the Firebird...or at least it's own hard drive. Also make sure that the server has a decen amount of ram...you'll need it.

 

[MasterRacker]

I can't add disks or RAM - the box is maxed out. I thought about sharing the RAID volume, I just want to make sure that I make the least impact on SQL as it takes precedence.

_____
Jeff
[small][purple]It's never too early to begin preparing for [/purple]International Talk Like a Pirate Day
"The software I buy sucks, The software I write sucks. It's time to give up and have a beer..." - Me[/small]

 

[macleod1021]

Well, you could try putting it on the E: drive.

Putting it on the C: is dangerous. If it gets out of control you could easily fill up your system drive and the server will come to a halt. In addition to that, your DB will be fighting with the system over disk access...this could affect the SQL Server.

If you put the Firebird database on the raid drive it will definatly affect the SQL Server...how much will depend on the activity the Firebird database sees.

The other issue that you're going to have is RAM. Typically, SQL Servers will cache data in RAM in order to make processing faster...this could cause perfrmance issues if the Firebird server isn't watched closely.

Depending on the setup of the raid drives and the expected amount of firebird database activity, you might beable to get away with putting it on the raid drive. Since your not able to upgrade the system at all, I'd guess that you're going to see a decrease in performance of the SQL Server...the amount of decrease will depend on a lot of factors. If the server has reasonably fast disk access, then you may be able to get by putting it on the raid drive.

I'd recommend doing some performance monitoring on the current firebird database to see how much activity it actually has...that will give you a better idea of whether or not the SQL box can handle it.

HTH

 

[MasterRacker]

The box it's on currently is also a SQL 2000 box. Our environment currently has a number of multi-purpose boxes. I had originally built the new SQL box to get better performance than any of the current ones, so I'm trying to minimize the impact.

_____
Jeff
[small][purple]It's never too early to begin preparing for [/purple]International Talk Like a Pirate Day
"The software I buy sucks, The software I write sucks. It's time to give up and have a beer..." - Me[/small]