Vfp nolock when updating sql

For every page accessed by a visitor, there is at least one row added to the table.

vfp nolock when updating sql-12vfp nolock when updating sql-78

If a page contains five references to graphics, there are six rows created in the logging table every time it is accessed.

The bottom-line is that because of the size of the table the report took too long to execute.

By default the data is logged in a text file, but you can alter the default behavior and log the data to an ODBC-compliant data store.

I used this approach for a client a while back because they wanted a simple way to track the activity for each major area of their site.

A major area was defined as the sections listed on the site's main navigation bar (e.g., Home, About Us, Services, ...).

The goal was to produce a report that showed the number of visits to each of the main areas of the site on a per month basis.SET NOCOUNT ON CREATE TABLE Source (Sou_ID int IDENTITY, Sou_Desc varchar(10)) go CREATE TRIGGER tr_Source_INSERT ON Source FOR INSERT AS PRINT GETDATE() go INSERT Source (Sou_Desc) VALUES ('Test 1') -- Results -- Apr 28 2001 AM This example is shown for illustrative purposes only.I'll cover an example later in the article that shows a real-world world use of triggers.The following shows how to modify the code to handle a multi-row INSERT.ALTER TRIGGER tr_Orders_INSERT ON Orders FOR INSERT AS IF EXISTS (SELECT * FROM inserted WHERE Ord_Priority = 'High') BEGIN DECLARE @Count tinyint SET @Count = (SELECT COUNT(*) FROM inserted WHERE Ord_Priority = 'High') PRINT CAST(@Count as varchar(3)) ' row(s) with a priority of High were entered' END go Those of you familiar with web site management know that counting the traffic on a site is key in determining which areas of the site are being used.The reason I decided to use a trigger-based solution had to do with the unacceptable execution time of the report.

Tags: , ,