August 17, 2004 at 11:44 pm
Hi,
In My company using sql server2000 for ERP product. Crystal also using in the same database.
Around 60 reports in the crystal. Using ASP to getting the reports.
Using frame in the html pages.
Aroung 32 users are connecting in the server. Opening the crystal report
its talking more than 5 mints. pl suggest me to get rid of from this problem.
Server pIV-2 GB ram, 2.6 ghz speed.
40 gb hdd.
Server is login server(DHCP) for network and shared folders also in this server, users accesing the shared folder.
ANY THING TO DO IN THE SQL SERVER TO MAKE UP SPEED.
Thanks & Regards
Uma Shankar.S
August 18, 2004 at 10:10 am
Why don't you try posting in a SQL Server 2000 newsgroup (which this one isn't)
Jamie Thomson
http://sqlblog.com/blogs/jamie_thomson
August 20, 2004 at 1:42 am
Which ERP System ?
Checked processor usage already ?
Disk writes ??? Which disks are you using ? Scsi ?
Had same problem when administrating. More memory and a fast NIC did the job.
Kind regards
El Jefe
JV
August 20, 2004 at 1:44 am
Which ERP System ?
Checked processor usage already ?
Disk writes ??? Which disks are you using ? Scsi ?
Had same problem when administrating. More memory and a fast NIC did the job.
And please use the server only for SQL 2000, not as domain controller or print and file sharing !!!!!!!!!!!!!!!!!
Kind regards
El Jefe
JV
August 20, 2004 at 10:59 am
Look for Lock problems.
Check statistics, update as necessary.
Reindex.
Use SPs over ad hoc T-SQL.
Limit joins - opt for temp tables where large, relatively static intermediate results are reused.
Break the problem down to specific queries, i bet it is a limited few that are the problem.
-------------------------------------
soapbox: Decaf coffee, much like a solar flashlight, is as useless as beer with no alcohol.
August 20, 2004 at 12:48 pm
Uma,
You've posted in the General topic for the SQL Server Yukon Beta forum. Which is what Jamie was trying to point out.
There are several different General subforums, so be careful which one you are posting in.
-SQLBill
August 23, 2004 at 8:54 am
This doesn't sound like a SQL problem, it sounds like a Crystal problem.
While Crystal is designed to simply "connect and create" reports against a database, it's notoriously slow if the report is even slightly complicated.
If Crystal is doing all of the work (sorting, summing, joining, etc) for these reports, 5 minutes for a report to produce results is not a lot, even with only 35 users.
Your reports will be much faster if you write a stored procedure to produce the desired results for each report, and use Crystal to display the results of the stored procedure.
You can verify this by copying the SQL code from one of Crystal reports and running it in Query Analyzier. If you get results back in seconds in QA, then you can be sure that it's Crystal.
Good Luck
Michael L John
If you assassinate a DBA, would you pull a trigger?
To properly post on a forum:
http://www.sqlservercentral.com/articles/61537/
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply