Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
Posted - 2007-02-14 : 08:30:36
|
| Cameron writes "Thanks for taking a look @ my question....Basically, is there an alternative to indexing that maintains the fast searching capability (or possibly faster)?We maintain over 500 databases on a single SQL server and currently (the way I am told) the server is limited to indexing 256 databases, so we have to basically create a new database with ALL the searchable data and use it for searches. While this works, it seems like there should be an alternate method. Any suggestions?Thank you for your time!" |
|
|
spirit1
Cybernetic Yak Master
11752 Posts |
Posted - 2007-02-14 : 10:32:30
|
alternative for indexing? no not really... maybe a full text index.server is limited to indexing 256 databases?? that's the first i heard of that.care to post any references to this?i find this hard to believe. maybe the issue is disk space?and 500 db's on one server work ok? that seems like a lot...Go with the flow & have fun! Else fight the flow blog thingie: http://weblogs.sqlteam.com/mladenp |
 |
|
|
mcrowley
Aged Yak Warrior
771 Posts |
|
|
Westley
Posting Yak Master
229 Posts |
Posted - 2007-02-15 : 05:03:09
|
| hard to imagine 500 DBs in a single server, if its all production, wouldn't it really slow? unless u got like a 16-ways cluster with like 100G of ram.....and diskspace will be huge....unless its 100M of each db...:) |
 |
|
|
|
|
|