Turn debugging on for your IP address and see how many milliseconds the page
takes to execute, then see how many milliseconds the SQL statements take to
execute, that way you can tell whether it is your SQL or your CF which is
the major part of the overhead.  If it is your SQL then ensure that your
Transact SQL has no big overhead - e.g. If you are using cursors in your SQL
code this will have a v.large overhead.  If however you are using ANSI
standard SQL (which it sounds like you are if you have mapped directly from
Access to SQL with no changes/additions) then I'm stuck as to what to
suggest.  It may come down to the ODBC drivers you are using - i.e. the ODBC
driver for access is "better" than the SQL one that you are using.  Try
swapping to OLEDB to see if this gives you any improvements although I'd be
very surprised if it did

-----Original Message-----
From: Jerry Staple [mailto:[EMAIL PROTECTED]]
Sent: 22 April 2002 16:33
To: CF-Talk
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 


************************************************************************
**********************

If you are not the intended recipient, or person responsible for
delivering it to the intended recipient, you are not authorized to and
must not disclose, copy, distribute or retain this message or any part
of it.

The opinions / views / comments on this e-mail do not necessarily
reflect any views or policies of biznet

The recipient should check this email and any attachments for the
presence of viruses. biznet accepts no liability for any damage caused
by any virus transmitted by this email. biznet 2001.

************************************************************************
**********************

 


 

 

 





______________________________________________________________________
Structure your ColdFusion code with Fusebox. Get the official book at 
http://www.fusionauthority.com/bkinfo.cfm
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists

Reply via email to