Re: How the SQL Server World Lives -- MIDRANGE-L

Subject: Re: How the SQL Server World Lives
From: rob@xxxxxxxxx
Date: Wed, 30 Jan 2013 08:54:27 -0500
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

Is it a hardware limitation (disk full) or is it a software limitation of
SQL server itself (limit on number of rows)? Or, it can hold them, but
it's a god awful nightmare waiting for the processing to get done?

I remember we waited too long on our old CISC dedicated EDI box to purge
transactions and had to reorg the database on a bigger box because that
one didn't have the space.

Or when we upgraded our AS/400's and processing time went so fast people
kept resubmitting their jobs because they weren't showing up on WRKACTJOB
(they were already done).

Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.