We are using a DB view in our project. This is the view which will be triggered many times in different reports. Initially data is coming fast but gradually the performance is getting down.

Can some one help us to improve the performance,

Thanks in advance.

Eswar

The memory usage is gradually increasing to the max value that is allocated to SQL Server.
Any suggestions?

I have sql 2008 R264 bit and 20 GB RAM but 19.7% ram is used by sqlservr.exe so any body know how to freez SQL 2008 R2 64 bit. Don’t tel me use AWE to allocate memory because it is not support on 64 bit

I have the same issue earlier, we found that SQL server wont release the unused memory once it complete the transactions or backups and this is a know issue. And in our case we found that we have application services run through out the clock and sending the data in xml’s to vendor server which is out of box so here they are occupying my RAM memory and never coming down, these services hit the DB to query in the open orders so obviously its SQL memory caching issue. so we tunned the services in background now the system is stand and calm.

So please check the any such services or applications which are connecting or using DB to query in continually.

And one point i need to add here, if you are using Windows server 2008 R2 have issue with the cache memory release please find the below

http://blogs.msdn.com/b/ntdebugging/archive/2007/11/27/too-much-cache.aspx

Patch released;

http://www.microsoft.com/downloads/en/details.aspx?FamilyID=E24ADE0A-5EFE-43C8-B9C3-5D0ECB2F39AF&displaylang=en

And there is also a SP1 released for the same

Good luck.

I have an issue with a server memory. SQL server is allocated 32 Gb out of 40 GB memory and sql server is using all the memory which is allocated to it.

The memory usage is gradually increasing to the max value that is allocated to SQL Server.
I have tried all ways but still no luck:

1. Killed all the open transactions.
2. Cleared the system cache.
3. Cleared session cache
4. Cleared procedure cache.
5. Checked for blocked transactions and killed them.
6. Ran DBCC opentran and found no open transactions.

The active connections to the server are as follows:

DatabaseName NoOfConnections LoginName

ReportServer 3 NT AUTHORITY\NETWORK SERVICE
master 21 sa
OLTP_QA_TEST 4 sa
KRApplication 1 sa
KYApplication 4 sa
DWH_QA_FINAL 1 sa
OLTP_QA_FINAL 2 sa

The Buffer info is as follows:

bpool_commit_target bpool_committed

I restrted the SQL server service and then memory went down but gradually it started increasing to theax value within one hour..

Can you please help me out in resolving this issue please.

One of the interviewer asked me about the database refresh.as per my knowledge i thought of backup and restore.

is iam correct.

As you said earlier article we can refresh the database by below dbcc commands,is iam right?

The following commands clean only the plan cache:
DBCC FREESYSTEMCACHE(All | pool_name)
DBCC FREESESSIONCACHE
DBCC FREEPROCCACHE
DBCC FLUSHPROCINDB( db_id )

To clear the data buffer use the following command:

DBCC DROPCLEANBUFFERS

At first I would like to make clear that there is difference in clearing of “Plan Cache” and “Data Buffer”. Plan Cache only contains the compiled and execution plans of sql statements, sp, function, etc. While all table data is stored in Data Buffer.
The following commands clean only the plan cache:
DBCC FREESYSTEMCACHE(All | pool_name)
DBCC FREESESSIONCACHE
DBCC FREEPROCCACHE
DBCC FLUSHPROCINDB( db_id )

To clear the data buffer use the following command:

DBCC DROPCLEANBUFFERS

For more information visit to : http://blog.sqlauthority.com/2007/03/23/sql-server-stored-procedure-clean-cache-and-clean-buffer/

Regards,
Pinal Dave

So when should we use these commands or when we should not? Will you explain me?

Thanks
Shailesh

If things are running slow and errors are occurring due to lack of memory on a production server – these commands are only short term band-aids and the real root of the problem needs to be found, analyzed, and fixed in order to have a well performing Production server.