Also, watch the locking. Make sure if there's select statements that you use the SET TRANSACTION ISOLATION LEVEL READ UNCOMMITTED to ensure a dirty read. You may be accidentally locking yourself out.
-----Original Message----- From: Jim McAtee [mailto:[EMAIL PROTECTED]] Sent: Monday, April 22, 2002 9:44 AM To: CF-Talk Subject: Re: Access /SQL Server Memory issues? MS SQL 2000 will use a lot more memory. When working with small tables and datasets you may be staying within the bounds of physical memory on the machine and never notice a difference. If you force the system to use virtual memory, though, the slowdown could be the effects of swapping to disk. Jim ----- Original Message ----- From: "Jerry Staple" <[EMAIL PROTECTED]> To: "CF-Talk" <[EMAIL PROTECTED]> Sent: Monday, April 22, 2002 9:33 AM Subject: RE: Access /SQL Server > Andy, > It is only selecting data and it is running on the same server as the > access versions? > > We would appreciate any advice. > > Jerry > > -----Original Message----- > From: Andy Ewings [mailto:[EMAIL PROTECTED]] > Sent: 22 April 2002 16:13 > To: CF-Talk > Subject: RE: Access /SQL Server > > > Sounds like the majority processing on this page is CF. Check the > debugging output and see how long the SQL queries take. If your SQL > queries are taking a noticable abmount of time then I'd suggest > ensuring that your indexes are correct and that your Transact SQL is > effecient. Without seeing > the code it's hard to suggest what it is. Is this page > inserting/updating/or deleting data? if so your indexes will increase > the > time it takes to execute the SQL statement and hence the page as all of > your > indexes have to be rebuilt when an action other than a select is > performed > on the table. > > -----Original Message----- > From: Jerry Staple [mailto:[EMAIL PROTECTED]] > Sent: 22 April 2002 16:08 > To: CF-Talk > Subject: Access /SQL Server > > > Hi, > We have recently migrated an access database to sql server 2000. > The transfer has gone great and the site runs quicker in 98% of the > site However there is one page (around 1500 lines of code) which > carries out allot of calculations and references 2 tables with about > 200000 records in each of them. We have found that the page still runs > quicker in an access database than a sql server db, we have also > checked indexes and created stored procedure for a number of the > queries. > > Can anyone tell me what we should check for as currently it is running > about 3 times slower? > > TIA > > > Jerry Staple > Web Application Developer > Certified Coldfusion (5.0) Developer > > > Head Office > 133-137 Lisburn Road, Belfast > Northern Ireland BT9 7AG > T +44 (0) 28 9022 3224 > F +44 (0) 28 9022 3223 > E [EMAIL PROTECTED] > W www.biznet-solutions.com ______________________________________________________________________ Your ad could be here. Monies from ads go to support these lists and provide more resources for the community. http://www.fusionauthority.com/ads.cfm FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
