September 8, 2010 at 12:58 am
For the past 1 week am facing his error in my Sql Server . Insufficient Memory to continue the excution of the program . It gets resolved when i restart the SQL Server Service . I cant find the in which case this error is occuring .
September 8, 2010 at 2:27 am
is this error you getting in some of your scheduled job and running queries?
If its on running queries then have you checked the bandwidth limitation with the server as well either the server is same domain or in different?
----------
Ashish
September 8, 2010 at 3:01 am
sir , i think it occurs on running queries only . i cant understand abt what you are meaning by domain . For your info , We have two 4 database servers . but we are facing this problem in only one Server which is a 64 bit server . Other 64 bit and 32 bit servers does not face any problem . The other Servers are also running on same Bandwith only .
September 8, 2010 at 3:31 am
1) Do you have disk space issue on that server?
2) Is the issue you gwetting on a specific query or any simple select statement as well?
3) Which version of sql server you have?
----------
Ashish
September 8, 2010 at 3:57 am
we are using SQL 2005 (64 Bit )Enterprise Edition . On thing i found was , Actually we are restoring a Database daily from our production Server to this server (Which is facing the problem as of now) which size is 86 GB . When i click Properties of Server it shows Size as 16 GB . But when i view the restored databse size it show a 86 GB . does this make any problem .
September 8, 2010 at 4:17 am
First of all why you are restoring database daily? You can configure log shipping for this or mirroring.
Also I am not able to understand what you mean by server size is 16 gb.
----------
Ashish
September 8, 2010 at 4:55 am
Actually this a reporting server . so to view reports we restore the production database from Production database to Report Server Daily . This is done to improve the performance of Prodcution Server and also we develop some simple applications in this Report Server for our MIS needs .
September 8, 2010 at 5:01 am
you can still do it by using log shipping. As its mainly used for reporting, it means database can be set to read only on secondary server and log can be restored on secondary server with every 10/15/20...... min of interval..
----------
Ashish
September 8, 2010 at 5:07 am
yes i have read this , but i dnt know hw to do it . but i will do it and tell you . will this be the reason for this error i have mentioned above . 16 GB i have mentioned is in SSMS when we right clickt the server name and go to Properties it will show Memory as Some xxxxxx MB. tats what i have mentioned .
September 8, 2010 at 5:28 am
restoring 86 gb on the server with 16gb of RAM should not be problem if, scheduled at the correct time when server is idle.
----------
Ashish
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply