Viewing 15 posts - 916 through 930 (of 1,409 total)
Could you rewrite the delete statement to:
DELETE TOP (20) FROM [dbo].[ServerParametersInstance]
WHERE Expiration < @now
This will prevent the query to simultaneously read and delete from the same table.
July 17, 2013 at 2:28 am
Run a trace when the deadlock occurs. In the trace you can specify the hostname, loginname, NT domain name, etc. to get more information about the connections involved in the...
July 17, 2013 at 2:23 am
You could read a little bit of information out of the default trace (if the timeframe hasn't been overwritten yet).
-- declare variable
declare @value sql_variant
-- get current tracefile of the default...
July 17, 2013 at 2:05 am
Krishna1 (7/17/2013)
folloing link shows maximum memory as 1GB http://msdn.microsoft.com/en-us/library/ms143685(v=sql.105).aspx
Aah, you didn't mention you are using the SQL Express version.
Yes, this version of SQL is limited to 1GB. You can probably...
July 17, 2013 at 1:40 am
Microsoft has excellent documentations online. Start at http://msdn.microsoft.com/en-us/library/bb545450.aspx
July 17, 2013 at 1:38 am
It sounds to me you have a "double-hop" issue at hand. Most of the time it's related to KERBEROS authentication and Active Directory. Your credentials are passed on from the...
July 17, 2013 at 1:35 am
Take a look at these two links:
Perhaps you can find some differences between both executions and pin-point the problem to specific wait-stats, (b)locking, etc.
July 17, 2013 at 1:25 am
Krishna1 (7/17/2013)
As per the msdn document max memory that can be allocated to any istance is 1GB.
Can you post a link to the MSDN article where you have read this?...
July 17, 2013 at 1:19 am
I think you should discuss this with the vendor. It could be that the application is keeping its own monitoring of the size and demands such free space. It could...
July 17, 2013 at 1:05 am
You can include the undocumented "sp_msforeachdb" in your code. Allthough this can have some odd behaviour. Aaron Bertrand has noticed this unexpected behaviour and created a more reliable version http://sqlblog.com/blogs/aaron_bertrand/archive/2010/12/29/a-more-reliable-and-more-flexible-sp-msforeachdb.aspx
July 17, 2013 at 12:48 am
The large difference in duration could be due to "parameter sniffing". When the SP is executed the first time (after reog indexes / update stats) an execution plan is generated....
July 17, 2013 at 12:22 am
As ScottPletcher allready pointed out, a negative result value indicates the first date in the DATEDIFF function is later then the second date.
Make sure you enter complete date (yyyymmdd) or...
July 17, 2013 at 12:00 am
I think a Powershell script could easaly return the information you want. I don't have such script at hand, but take a look at the Technet Scriptcenter http://gallery.technet.microsoft.com/ScriptCenter/ for many...
July 16, 2013 at 9:27 am
Each instance you are installing on a cluster needs their own cluster group. You can't use the same cluster group for multiple SQL instances. Each cluster group for SQL must...
July 16, 2013 at 12:45 am
Viewing 15 posts - 916 through 930 (of 1,409 total)