I am not pretending in any way to be an expert here, but...
the company I work for uses sql server (on an NT platform) as the back end of a time-based billing software for lawfirms. SQL Server seems to work o-k for the day to day transactions, but we have no end of problems in the conversion phase before a firm goes live. Raising indexes, simple queries, dbccs and the like - really simple stuff - can take hours (or days) on a 20-30 gig DB.
Now, I don't know if the problems here lie in the way our install group sets up the software, or if this is just to be expected - but my experience is that sql server just doesn't handle medium to large datasets very well at all.
Slashdot Mirror
I am not pretending in any way to be an expert here, but...
the company I work for uses sql server (on an NT platform) as the back end of a time-based billing software for lawfirms. SQL Server seems to work o-k for the day to day transactions, but we have no end of problems in the conversion phase before a firm goes live. Raising indexes, simple queries, dbccs and the like - really simple stuff - can take hours (or days) on a 20-30 gig DB.
Now, I don't know if the problems here lie in the way our install group sets up the software, or if this is just to be expected - but my experience is that sql server just doesn't handle medium to large datasets very well at all.