SQL*NET = Computer Death

From: Jay Szewczyk <james_szewczyk_at_ccnpp.bge.com>
Date: 17 Nov 1994 14:32:06 GMT
Message-ID: <3afph6$gj6_at_news1.digex.net>


We have running:

	HP T500 4way(lots of guts)
	Oracle 7.1.3

We are about cut-loose 1600 people onto this new box and application. In simulation everything runs great....until, the reports start to come in. Coming down from a mainframe the users are akin to adhok reporting in focus. So, to provide baseline service we had to give the users a method of adhok: Oracle Data Browser for Windows. Along with the canned V2 reports and Data B., Our system is taking a beating. We are working on a way to batch reports coming from the application using the UNIX Batch command. Using batch, we think we can queue the reports from the app., allowing only 2 to run at one time during peak hours. I'm interested in hearing other ways admins have successfully controlled/batched reports.

This still doesn't cover the Data Browser reports. Have we given to much power to the user? Is it a matter of educating the user in the realities of downsized systems? It is already clear that letting users write their own reports, esspecially with a very new reporting tool is going to be a problem. It was a problem on the mainframe. We(IS and the user), in time, will both evolve in that respect.

Bottom line: How do we put a lid on Joe and his SQL*NET connection doing

             full table scans in Microsoft access.

Times are a changing.....

JAY
james_szewczyk_at_ccnpp.bge.com Received on Thu Nov 17 1994 - 15:32:06 CET

Original text of this message