Post reply

SQL Server 7.0 - Number of Databases

  • March 26, 2007 at 2:29 am

    #62364

    Hi there

    Is there a limit to the amount of databases that can be on SQL 7.0 before one starts to have performance issues? I remember years ago that we started running into issues once we passed the 400 mark, so we detached a lot of the older ones. Is this a hardware or software limitation?

    Kindest Regards,

    <hr noshade size='1' width='250' color='#BBC8E5'>Kindest Regards,

    Roelof
    <a href='http://' class='authorlink' target='_blank'></a>

    --There are only 10 types of people in the world. Those who understand binary, and those who don't.

  • March 26, 2007 at 4:24 am

    #696830

    SQL 7 and 2000 have a limit of 32767 databases per instance. I don't think anyone ever reached this limit. So in your case I suspect that the server hardware was the limiting factor.

    Markus

    [font="Verdana"]Markus Bohse[/font]

  • March 26, 2007 at 4:26 am

    #696831

    I'm not aware of an actual limitation, although I've not used SQL Server 7 for a long time now!

    I must admit, I have not worked on an instance with more than 30 databases previously.

    How busy are the databases is the key question.  If you have a lot of busy databases then yes, hardware could come into the equation.  Although rather than throwing money at hardware, I would first look to tune the databases using the most IO.

  • March 26, 2007 at 4:37 am

    #696832

    Thanks...

    The most annoying performance issue reported to me was when accessing the server with Enterprise Manager, apparently some people still do .

    <hr noshade size='1' width='250' color='#BBC8E5'>Kindest Regards,

    Roelof
    <a href='http://' class='authorlink' target='_blank'></a>

    --There are only 10 types of people in the world. Those who understand binary, and those who don't.

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply