Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Technology Stocks : How high will Microsoft fly? -- Ignore unavailable to you. Want to Upgrade?

To: ericneu who wrote (35262)	12/9/1999 8:10:00 PM
From: Daniel Schuh	Read Replies (3) \| Respond to of 74651

Well, if it ain't SQL Server, then that leaves NT, eh? Anyway, benchmarks aren't everything.

To: ericneu who wrote (35262)	12/9/1999 8:41:00 PM
From: Lizzie Tudor	Read Replies (2) \| Respond to of 74651

I've experienced basic database errors on SI related to logfile allocation. When this happens on Oracle you get performance problems and all kinds of stuff, and inability to write to the database. Maybe these are just dba issues (vs. problems with the server itself)... or implementation matters, I'm not sure, but it looks to me like dbms issues... (I can also tell by the references to sp_extendsegment that this is SQL server and not Oracle) * fsUtilMsgPreviewSubmit: Can't allocate space for object 'Syslogs' in database 'qcomstock' because the 'logsegment' segment is full. If you ran out of space in Syslogs, dump the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to increase the size of the segment. Severity 17, State 2, Procedure 'gargantua updateSnapshot', Line 3 www2.techstocks.com