SQL Server Limitations?

[Fareed Ahamed]

Hi,

Is there any limitations in the volume of data i.e. size of the table ? I'm
using MTS components
for transactions but it is blocking the CPU time (mtx.exe taking 99 cpu time).
Current database size is
2.3 GB

Thanks in advance...

Cheers
Fareed

[Tom Shreve]

You didn't specify your database, but most relational databases easily support
millions of rows (e.g., SQL Server, Oracle, UDB, etc). Access and other "desktop"
databases have a much lower practical limit (e.g., 100,000 rows).

As to CPU utilization for mtx.exe, is the database on the same machine? If
not, then there's something fishy with either your component in MTS or with
how MTS is configured. I'm assuming your database server is a different machine.

My guess is that the problem is somehow related to the fact that you're using
MTS to manage your transactions. If you move transaction management to the
database server(s), my guess is the MTS component will sit idle while the
query is processing, waiting for it to return. If not, then you've ruled
out a class of potential problems related to MTS transactions.

I would guess that if you use a complex transactional object model in MTS
(i.e., many objects created within the context of a particular transaction),
that mtx.exe has to work harder to manage the transactions. It can also be
easy to design poor data access using MTS transactions because it's a bit
foreign until you work with it a while. Like Visual Basic, it's easy to abuse.

Recommendation: move transactions into the database server or simplify your
MTS transactions somehow to see if it alleviates the problem.

Tom

"Fareed Ahamed" <fareedsattar@hotmail.com> wrote:
>
>Hi,
>
>Is there any limitations in the volume of data i.e. size of the table ?
I'm
>using MTS components
>for transactions but it is blocking the CPU time (mtx.exe taking 99 cpu
time).
>Current database size is
>2.3 GB
>
>Thanks in advance...
>
>Cheers
>Fareed