Viewing 13 posts - 1 through 13 (of 13 total)
As you are selecting all the records, you may have to look at the client machine's available memory and cpu usage. Try to run the query in SQL Server box...
November 14, 2005 at 8:39 pm
Look at the eventlog and see any errors related to HBA Connectivity error or warning.
October 21, 2005 at 12:29 pm
After DBCC DBREINDEX the space can be scattered, it wont reduce the size of the database file. Then have to shrink the database file by moving the free space using...
August 12, 2005 at 10:18 am
Hi,
This may help you..
http://www.mssqlcity.com/Articles/SQL65/PageStr/SQL65PageStr.htm
This is for SQL Server 6.4. I think this should be the same for the later versions. Let us know if you find anything...
May 31, 2005 at 1:13 am
It is always better to run dbcc dbreindex while there are no transactions on the corresponding tables as it locks the entire schema. Do not schedule it in maintenance plan...
May 17, 2005 at 10:52 pm
Hi, I dont know in which scenario you are getting this error. But I am sure this could be related to backup destination location issue, may be out of space...
May 17, 2005 at 1:37 pm
This is found in SQL Server Books on-line. Initially we had 4 GB (3 GB for SQL + 1 GB for OS) with AWE Option disabled. Once we upgraded from...
May 17, 2005 at 1:27 pm
Chris,
OH God..
We had this issues and there is solution found in Microsoft support pages..this is the reason we think SP4 is the solution to fix AWE Issues. We are not...
May 17, 2005 at 12:43 pm
Hi, Check this link
http://support.microsoft.com/default.aspx?scid=kb;en-us;263889
may help you understand most of the cases...
May 17, 2005 at 12:54 am
Hi, There are number of reasons the procedure is getting recompiled.
These are some of the reasons with reference to your code here..
1. Procedure cache is not in memory. somebody might...
May 17, 2005 at 12:50 am
Hi, If you have AWE enabled, you should have installed the SP4. We have deployed SP4 on a production server and we are not seeing any issues related to AWE....
May 16, 2005 at 1:35 pm
Hi,
1. backup the log and try to shrink it.
2. If you have replication set with any of the tables that went heavy transactions and if
your replication log-reader is...
May 15, 2005 at 11:13 pm
Rafeeque,
You dont really need to restart the sql server first of all.
My assumption is, there are some database procedure/call uses tempdb heavily and it requires 6.2 GB maximum. and...
May 15, 2005 at 10:26 pm
Viewing 13 posts - 1 through 13 (of 13 total)