December 5, 2005 at 2:52 pm
A design question:
We will have a new feature that includes using a text search on a table of documents (word, ppt, etc).
Will it improve performance if the table is part of a different database (but same sql server) than the application is belongs to?
Thanks for any info. If there is a document out that refers to this please send too.
December 5, 2005 at 4:19 pm
If you house the database on the same SQL Server, using the same physical disks than I would say no. The fact that this means that both databases would be sharing CPU, disk, and memory tells me that long running queries against this secondary database would degrade performance in your main database.
In order to truely split this off and still use the same physical SQL Server, you could use a named instance of SQL Server. This would allow you to control, somewhat, the resources that you would want to devote to this text search database. You could split your memory resources up between instances using max server memory. You would also need to move this text search DB off to it's own set of physical disks to avoid I/O contention.
I do not have specific experience using named instances in this manner, so need to get further input from forum members with experience in this area. I would suggest, at the bare minimum, to move this new DB off to it's own disks.
December 5, 2005 at 6:24 pm
I worked for a dot.com where the director issued an edict that there would be only one database – end of discussion. He cited performance gains repeatedly; but it was never totally clear whether this was the case or whether he was just sick and tired of stovepipe applications. In the end there were still stovepipes; but they were all within one database. Perhaps this could lead to some efficiency if and when a data architect decided to get to work. It will be interesting to hear what you decide.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply