Showing posts with label memory. Show all posts
Showing posts with label memory. Show all posts

Monday, March 19, 2012

Access Violation occurred writing address

Hi folks,
It seems for the last few days my SQL Server has been producing memory dumps
(with errors) about three times a day.
The main error seems to be the following :-
Computer type is AT/AT COMPATIBLE.
Current time is 22:11:16 09/20/05.
1 Intel x86 level 15, 3 Mhz processor(s).
Windows NT 5.0 Build 2195 CSD Service Pack 4.
Memory
MemoryLoad = 75%
Total Physical = 991 MB
Available Physical = 240 MB
Total Page File = 2926 MB
Available Page File = 2269 MB
Total Virtual = 2047 MB
Available Virtual = 980 MB
*Stack Dump being sent to C:\Program Files\Microsoft SQL
Server\MSSQL\log\SQLDu
mp0029.txt
*
************************************************** ***************************
**
*
* BEGIN STACK DUMP:
* 09/20/05 22:11:16 spid 0
*
* Exception Address = 004093CA
* Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
* Access Violation occurred writing address 00000807
This error with differing memory address happens twice a day at various
times of the day, I had hoped it was linked to server usage however this
doesnt seem the case.
This SQL Server is used as the backend of an Online Web Browser game, and
typically its most active in the evenings however it seems to produce these
errors at any time of the day.
Although if it errors in the morning it wont do it in the evening ... but
then if it errors in the evening it doesnt do it in the morning.
Its almost like SQL is playing up for attention but its not speaking a
language I know.
Does anyone have any Ideas, any help greatly appreciated.
Thanks
Hi
We had this for a while on one of our servers.
We rebuilt all the indexes on all the databases and the problem went away.
Regards-
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Daniel Paull" <DanielPaull@.discussions.microsoft.com> wrote in message
news:7B5217FF-4635-47DC-8F0C-4208A21E99C4@.microsoft.com...
> Hi folks,
> It seems for the last few days my SQL Server has been producing memory
> dumps
> (with errors) about three times a day.
> The main error seems to be the following :-
> Computer type is AT/AT COMPATIBLE.
> Current time is 22:11:16 09/20/05.
> 1 Intel x86 level 15, 3 Mhz processor(s).
> Windows NT 5.0 Build 2195 CSD Service Pack 4.
>
> Memory
> MemoryLoad = 75%
> Total Physical = 991 MB
> Available Physical = 240 MB
> Total Page File = 2926 MB
> Available Page File = 2269 MB
> Total Virtual = 2047 MB
> Available Virtual = 980 MB
> *Stack Dump being sent to C:\Program Files\Microsoft SQL
> Server\MSSQL\log\SQLDu
> mp0029.txt
> *
> ************************************************** ***************************
> **
> *
> * BEGIN STACK DUMP:
> * 09/20/05 22:11:16 spid 0
> *
> * Exception Address = 004093CA
> * Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
> * Access Violation occurred writing address 00000807
> This error with differing memory address happens twice a day at various
> times of the day, I had hoped it was linked to server usage however this
> doesnt seem the case.
> This SQL Server is used as the backend of an Online Web Browser game, and
> typically its most active in the evenings however it seems to produce
> these
> errors at any time of the day.
> Although if it errors in the morning it wont do it in the evening ... but
> then if it errors in the evening it doesnt do it in the morning.
> Its almost like SQL is playing up for attention but its not speaking a
> language I know.
> Does anyone have any Ideas, any help greatly appreciated.
> Thanks
|||Hi thanks for the reply,
Did you use DBCC DBREINDEX or physically drop and recreate the indexes ?

Access Violation occurred writing address

Hi folks,
It seems for the last few days my SQL Server has been producing memory dumps
(with errors) about three times a day.
The main error seems to be the following :-
Computer type is AT/AT COMPATIBLE.
Current time is 22:11:16 09/20/05.
1 Intel x86 level 15, 3 Mhz processor(s).
Windows NT 5.0 Build 2195 CSD Service Pack 4.
Memory
MemoryLoad = 75%
Total Physical = 991 MB
Available Physical = 240 MB
Total Page File = 2926 MB
Available Page File = 2269 MB
Total Virtual = 2047 MB
Available Virtual = 980 MB
*Stack Dump being sent to C:\Program Files\Microsoft SQL
Server\MSSQL\log\SQLDu
mp0029.txt
*
****************************************
************************************
*
**
*
* BEGIN STACK DUMP:
* 09/20/05 22:11:16 spid 0
*
* Exception Address = 004093CA
* Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
* Access Violation occurred writing address 00000807
This error with differing memory address happens twice a day at various
times of the day, I had hoped it was linked to server usage however this
doesnt seem the case.
This SQL Server is used as the backend of an Online Web Browser game, and
typically its most active in the evenings however it seems to produce these
errors at any time of the day.
Although if it errors in the morning it wont do it in the evening ... but
then if it errors in the evening it doesnt do it in the morning.
Its almost like SQL is playing up for attention but its not speaking a
language I know.
Does anyone have any Ideas, any help greatly appreciated.
ThanksHi
We had this for a while on one of our servers.
We rebuilt all the indexes on all the databases and the problem went away.
Regards-
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Daniel Paull" <DanielPaull@.discussions.microsoft.com> wrote in message
news:7B5217FF-4635-47DC-8F0C-4208A21E99C4@.microsoft.com...
> Hi folks,
> It seems for the last few days my SQL Server has been producing memory
> dumps
> (with errors) about three times a day.
> The main error seems to be the following :-
> Computer type is AT/AT COMPATIBLE.
> Current time is 22:11:16 09/20/05.
> 1 Intel x86 level 15, 3 Mhz processor(s).
> Windows NT 5.0 Build 2195 CSD Service Pack 4.
>
> Memory
> MemoryLoad = 75%
> Total Physical = 991 MB
> Available Physical = 240 MB
> Total Page File = 2926 MB
> Available Page File = 2269 MB
> Total Virtual = 2047 MB
> Available Virtual = 980 MB
> *Stack Dump being sent to C:\Program Files\Microsoft SQL
> Server\MSSQL\log\SQLDu
> mp0029.txt
> *
> ****************************************
**********************************
***
> **
> *
> * BEGIN STACK DUMP:
> * 09/20/05 22:11:16 spid 0
> *
> * Exception Address = 004093CA
> * Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
> * Access Violation occurred writing address 00000807
> This error with differing memory address happens twice a day at various
> times of the day, I had hoped it was linked to server usage however this
> doesnt seem the case.
> This SQL Server is used as the backend of an Online Web Browser game, and
> typically its most active in the evenings however it seems to produce
> these
> errors at any time of the day.
> Although if it errors in the morning it wont do it in the evening ... but
> then if it errors in the evening it doesnt do it in the morning.
> Its almost like SQL is playing up for attention but its not speaking a
> language I know.
> Does anyone have any Ideas, any help greatly appreciated.
> Thanks|||Hi thanks for the reply,
Did you use DBCC DBREINDEX or physically drop and recreate the indexes ?

Access Violation occurred writing address

Hi folks,
It seems for the last few days my SQL Server has been producing memory dumps
(with errors) about three times a day.
The main error seems to be the following :-
Computer type is AT/AT COMPATIBLE.
Current time is 22:11:16 09/20/05.
1 Intel x86 level 15, 3 Mhz processor(s).
Windows NT 5.0 Build 2195 CSD Service Pack 4.
Memory
MemoryLoad = 75%
Total Physical = 991 MB
Available Physical = 240 MB
Total Page File = 2926 MB
Available Page File = 2269 MB
Total Virtual = 2047 MB
Available Virtual = 980 MB
*Stack Dump being sent to C:\Program Files\Microsoft SQL
Server\MSSQL\log\SQLDu
mp0029.txt
*
*****************************************************************************
**
*
* BEGIN STACK DUMP:
* 09/20/05 22:11:16 spid 0
*
* Exception Address = 004093CA
* Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
* Access Violation occurred writing address 00000807
This error with differing memory address happens twice a day at various
times of the day, I had hoped it was linked to server usage however this
doesnt seem the case.
This SQL Server is used as the backend of an Online Web Browser game, and
typically its most active in the evenings however it seems to produce these
errors at any time of the day.
Although if it errors in the morning it wont do it in the evening ... but
then if it errors in the evening it doesnt do it in the morning.
Its almost like SQL is playing up for attention but its not speaking a
language I know.
Does anyone have any Ideas, any help greatly appreciated.
ThanksHi
We had this for a while on one of our servers.
We rebuilt all the indexes on all the databases and the problem went away.
Regards-
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Daniel Paull" <DanielPaull@.discussions.microsoft.com> wrote in message
news:7B5217FF-4635-47DC-8F0C-4208A21E99C4@.microsoft.com...
> Hi folks,
> It seems for the last few days my SQL Server has been producing memory
> dumps
> (with errors) about three times a day.
> The main error seems to be the following :-
> Computer type is AT/AT COMPATIBLE.
> Current time is 22:11:16 09/20/05.
> 1 Intel x86 level 15, 3 Mhz processor(s).
> Windows NT 5.0 Build 2195 CSD Service Pack 4.
>
> Memory
> MemoryLoad = 75%
> Total Physical = 991 MB
> Available Physical = 240 MB
> Total Page File = 2926 MB
> Available Page File = 2269 MB
> Total Virtual = 2047 MB
> Available Virtual = 980 MB
> *Stack Dump being sent to C:\Program Files\Microsoft SQL
> Server\MSSQL\log\SQLDu
> mp0029.txt
> *
> *****************************************************************************
> **
> *
> * BEGIN STACK DUMP:
> * 09/20/05 22:11:16 spid 0
> *
> * Exception Address = 004093CA
> * Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
> * Access Violation occurred writing address 00000807
> This error with differing memory address happens twice a day at various
> times of the day, I had hoped it was linked to server usage however this
> doesnt seem the case.
> This SQL Server is used as the backend of an Online Web Browser game, and
> typically its most active in the evenings however it seems to produce
> these
> errors at any time of the day.
> Although if it errors in the morning it wont do it in the evening ... but
> then if it errors in the evening it doesnt do it in the morning.
> Its almost like SQL is playing up for attention but its not speaking a
> language I know.
> Does anyone have any Ideas, any help greatly appreciated.
> Thanks|||Hi thanks for the reply,
Did you use DBCC DBREINDEX or physically drop and recreate the indexes ?

Thursday, March 8, 2012

Access to SQL Server 2k database is slow

My SQL server was just upgraded from 7.0 to 2000. It was having memory leak
problems before, so it was upgrade to 2000 by the agency that over sees our
databases. Now the access time to the database is pretty slow when trying to
pull up information. Our custom client software loads fine and connects to
the database, but we when we do a search or try to open a particular case
(we are a court) from the database, it takes almost 30 seconds before any
information comes up. No error messages are returned. It is just a slow
response time. Sql server 2k is installed on a w2k server and the clients
are running XP pro, with 100mb/full duplex on a switch. I am not familiar
enough with sql server so I wouldn't exactly what to look for or what kind
of commands to run for running the Profiler or Query Analzyer.
I would appreciate any help anybody could provide. In case your wondering,
the guy who did the upgrade decided to take 3 days off after doing this on
the weekend, don't ask me why? I am the tech person for the agency, just no
familiar with sql server. Again, thanks for any help or advice.Make sure the autoclose database option is not set to on. You can check this
out in enterprise manager, right click on your database and then go to
options. If this is not your problem, I think you're going to have to run
your query manuaaly from query analyzer to see if the problem is within sql
server or outside.
Carlos E. Rojas
SQL Server MVP
Co-Author SQL Server 2000 programming by Example
"Vegeta" <vegeta@.whocares.com> wrote in message
news:%23BhI6Y2CEHA.3408@.tk2msftngp13.phx.gbl...
> My SQL server was just upgraded from 7.0 to 2000. It was having memory
leak
> problems before, so it was upgrade to 2000 by the agency that over sees
our
> databases. Now the access time to the database is pretty slow when trying
to
> pull up information. Our custom client software loads fine and connects to
> the database, but we when we do a search or try to open a particular case
> (we are a court) from the database, it takes almost 30 seconds before any
> information comes up. No error messages are returned. It is just a slow
> response time. Sql server 2k is installed on a w2k server and the clients
> are running XP pro, with 100mb/full duplex on a switch. I am not familiar
> enough with sql server so I wouldn't exactly what to look for or what kind
> of commands to run for running the Profiler or Query Analzyer.
> I would appreciate any help anybody could provide. In case your wondering,
> the guy who did the upgrade decided to take 3 days off after doing this on
> the weekend, don't ask me why? I am the tech person for the agency, just
no
> familiar with sql server. Again, thanks for any help or advice.
>|||The autoclose database option was not set to on. I also just saw that sql
server
2k had no service packs installed. I will be backing up my database and
installing
sql 2k SP3a. Maybe this could help it some.
Thanks for you response.
"Carlos Eduardo Rojas" <carloser@.mindspring.com> wrote in message
news:%23tdVxG4CEHA.3804@.TK2MSFTNGP09.phx.gbl...
> Make sure the autoclose database option is not set to on. You can check
this
> out in enterprise manager, right click on your database and then go to
> options. If this is not your problem, I think you're going to have to run
> your query manuaaly from query analyzer to see if the problem is within
sql
> server or outside.
> --
> Carlos E. Rojas
> SQL Server MVP
> Co-Author SQL Server 2000 programming by Example
>
> "Vegeta" <vegeta@.whocares.com> wrote in message
> news:%23BhI6Y2CEHA.3408@.tk2msftngp13.phx.gbl...
> leak
> our
trying
> to
to
case
any
clients
familiar
kind
wondering,
on
> no
>|||On 2004-03-16, Vegeta <vegeta@.whocares.com> wrote:
> The autoclose database option was not set to on. I also just saw that sql
> server
> 2k had no service packs installed. I will be backing up my database and
> installing
> sql 2k SP3a. Maybe this could help it some.
>
Try updating MDAC on the client machines. I had the same problems on some
machines at my company, though we're running Win2k on most of clients.
Mike
--
"I can do it quick. I can do it cheap. I can do it well. Pick any two."
Mario Splivalo
msplival@.jagor.srce.hr