Damn! At least I know this ahead of time. Our db has almost no indexes
(just the primary keys really) and because of the 900 byte index limit I
can't create indexes on the fields that we would be frequently searching
on. But at least since have have few indexes and rows don't go through
multiple table joins, we should have high insert rates.
I didn't know about sqlpass.org. Thanks for the tip!
On Fri, 21 May 2004 10:21:47
[quoted text, click to view] -0400, Geoff N. Hiten wrote:
> No. Each SQL Server\instance has exclusive control over its databases.
Why would you need more than 900 bytes in an index key? Anything that large
really needs to go to full-text search instead.
--
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org [quoted text, click to view] "Jack Victor" <Nomail@JustPostReply.tv> wrote in message
news:pan.2004.05.21.15.40.12.152000@JustPostReply.tv...
> Damn! At least I know this ahead of time. Our db has almost no indexes
> (just the primary keys really) and because of the 900 byte index limit I
> can't create indexes on the fields that we would be frequently searching
> on. But at least since have have few indexes and rows don't go through
> multiple table joins, we should have high insert rates.
>
> I didn't know about sqlpass.org. Thanks for the tip!
>
>
> On Fri, 21 May 2004 10:21:47
> -0400, Geoff N. Hiten wrote:
>
> > No. Each SQL Server\instance has exclusive control over its databases.
>