Re: 64bit insert delays
From: Tibor Karaszi (tibor_please.no.email_karaszi_at_hotmail.nomail.com)
Date: 12/20/04
- Next message: Tibor Karaszi: "Re: 64bit insert delays"
- Previous message: Nigel Rivett: "RE: Simple Problem - Simple Solution?"
- In reply to: Paul Durrant: "Re: 64bit insert delays"
- Next in thread: Paul Durrant: "Re: 64bit insert delays"
- Reply: Paul Durrant: "Re: 64bit insert delays"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 20 Dec 2004 17:11:24 +0100
Start with running a simple SELECT statement against the table you INSERT into instead of checking
that the data is there with the web page. First step is to determine where the actual problem is...
-- Tibor Karaszi, SQL Server MVP http://www.karaszi.com/sqlserver/default.asp http://www.solidqualitylearning.com/ "Paul Durrant" <PaulDurrant@discussions.microsoft.com> wrote in message news:C5D73090-78ED-4162-8972-A010AF7327B7@microsoft.com... > the system logs all emails through are mail servers, we have a web page that > we/users can query when mails were processed by the antispam system, om the > antispam system, the key data is written to the eventlog, and we can compare > when the mail was processed and when the data becomes available to the web > page query > > i have been looking at this for some time now, i can see the transaction > going through via the profiler, but when the web page queries the DB there > are no results till a few minutes later > > > > > "Tibor Karaszi" wrote: > >> I've never seen or heard about this, which makes me think that something else is going on. What >> way >> to you determine that the row you inserted isn't available until after a few minutes? Do you >> select >> all the rows and count number of rows or looking for a certain known value using a WHERE clause? >> To >> me, this sounds like you are selecting from some other table than the one inserting into and you >> have some type of replication process which is lagging. Anyhow, I think we need more detail (see >> above questions) in order to comment more on this... >> >> -- >> Tibor Karaszi, SQL Server MVP >> http://www.karaszi.com/sqlserver/default.asp >> http://www.solidqualitylearning.com/ >> >> >> "Paul Durrant" <PaulDurrant@discussions.microsoft.com> wrote in message >> news:0D55EF92-FB7E-469F-AF27-BD7D45D20269@microsoft.com... >> > that is correct >> > >> > the inserted data includes a getdate() and the time of the insert is >> > correct, so its clearly the transaction log that is running behind. >> > >> > >> > >> > "Tibor Karaszi" wrote: >> > >> >> Are you saying that you perform an INSERT and after that a SELECT and the SELECT doesn't show >> >> the >> >> new data until after some 5 minutes? Can you reproduce this using SQL commands from Query >> >> analyzer? >> >> >> >> -- >> >> Tibor Karaszi, SQL Server MVP >> >> http://www.karaszi.com/sqlserver/default.asp >> >> http://www.solidqualitylearning.com/ >> >> >> >> >> >> "Paul Durrant" <PaulDurrant@discussions.microsoft.com> wrote in message >> >> news:F3775D2F-1122-4118-AC49-342759B7A8C8@microsoft.com... >> >> > we a system fed by various sources (foxpro,dotnet,ado) and we are seeing >> >> > delays in the data being available, there are no insert errors, but the data >> >> > does not appear for selection for at least 5 minutes >> >> > >> >> > >> >> >> >> >> >> >> >> >>
- Next message: Tibor Karaszi: "Re: 64bit insert delays"
- Previous message: Nigel Rivett: "RE: Simple Problem - Simple Solution?"
- In reply to: Paul Durrant: "Re: 64bit insert delays"
- Next in thread: Paul Durrant: "Re: 64bit insert delays"
- Reply: Paul Durrant: "Re: 64bit insert delays"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
