Re: Slow initial record write
From: Keith Kratochvil (sqlguy.back2u_at_comcast.net)
Date: 12/06/04
- Next message: StefanT: "Re: Sql Server instalation on a Windows 2003 Server"
- Previous message: Keith Kratochvil: "Re: migrate SQL 7 to 2000"
- In reply to: joeblues: "Re: Slow initial record write"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 6 Dec 2004 12:24:00 -0600
That message is not all that meaningful (or important).
-- Keith "joeblues" <joeblues@discussions.microsoft.com> wrote in message news:74D47BBF-EC88-4FCB-AB25-5613989A85FD@microsoft.com... > Keith, > > I ran the specified query and found that the current state is for > 'autoclose' as 'off' so I guess this isn't the issue. > > The application software that we are using is made by Exact Software and it > is their product Alliance Manufacturing. The software works with either > Access databases or SQL ones. > > I have asked the application software people and they don't have a clue. > They feel that it is a SQL configuration question (naturally) and sort of > pass the buck on it. > > We have also had a few instances lately where the software has stalled out > during the day. After a wait it eventually goes through, but it is > aggravating when it happens. > > When it happened today, I went to the fileserver Event Viewer and looked to > see if there were any related errors. There was one message that referred > directly to the SQL server and it was as follows: > > Error: 15457, Severity: 0, State: 1 > Configuration option 'show advanced options' changed from 1 to 1. Run > the RECONFIGURE statement to install. > > Is this meaningful to you at all? > > Thanks for the help so far. > > Joe > > "Keith Kratochvil" wrote: > > > Perhaps Autoclose is set "on" > > > > To find out execute the following within Query Analyzer: > > exec sp_dboption 'YourDatabaseNameGoesHere', 'autoclose' > > > > If the CurrentSetting is "on" that means that autoclose is set on. You can > > read about autoclose within Books Online, but generally you want to leave it > > off. > > > > To turn autoclose off: > > exec sp_dboption 'YourDatabaseNameGoesHere', 'autoclose', 'off' > > > > How do you insert, update, or delete? Stored procedures? Is the problem > > repeatable within Query Analyzer? Before you insert, update, or delete data > > does your application retrieve data first? If autoclose is set on and you > > don't retrieve data (and open the database) the time you have to wait could > > be due to the database starting up. What database access method are you > > using? What type of application are you using to access/modify data within > > SQL Server? > > > > -- > > Keith > > > > > > "joeblues" <joeblues@discussions.microsoft.com> wrote in message > > news:C31E1A4B-F68F-4E25-BD8D-E48782E56BF4@microsoft.com... > > > Using SQL server 2000 with third party application software. If database > > has > > > no activity for a period of time (maybe a few hours or so), the first time > > we > > > try to change, delete or write a record to the database it takes four to > > > seven minutes to accept the record write. > > > > > > You can browse records at a normal pace, but any kind of activity that > > > requires a change to a record in the database experiences this delay. > > After > > > this initial record is handled, activity is just fine and the very next > > > record will go through nice and quick. > > > > > > Is there any kind of standby or idle state that the SQL server might go > > > through if it is inactive for a period of time? Can this be adjusted or > > > changed? > > > >
- Next message: StefanT: "Re: Sql Server instalation on a Windows 2003 Server"
- Previous message: Keith Kratochvil: "Re: migrate SQL 7 to 2000"
- In reply to: joeblues: "Re: Slow initial record write"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
|