I have a windows Server 2008 R2 cluster and I would like to be able to distinguish between a user initiated failover and a failover caused be a resource check failing.
I was hoping that the cluster service would write this information to the event log; but it appears this is not occurring. is there any way to make the cluster service write an event to the event log when a failover occurs?
I have a sql server job that is scheduled to run every 3 hours. Occasionally, the job takes longer than 3 hrs. In that case, the next scheduled run does not occur.
I would like to setup sql server to alert me if this conditions occurs and perhaps log the condition.
We are preparing to implement transactional replication between two of our sql servers.
The server that will act as the publisher and distributor is an x64 sql server 2005 standard. The subscriber is an x64 sql server 2008 sp1 enterprise.
Does anyone have a checklist of things information that we need to configure this?
I would also like to see if anyone has any scripts to verify that things are working correctly
We have an ETL job that from time to time gets hung up.
in this case, I looked in sp_who2 and there was no blocking, and it was the only active query on the system.
Here is a dump from sysprocesses:
spid kpid blocked waittype waittime lastwaittype waitresource dbid uid cpu physical_io memusage login_time last_batch ecid open_tran status cmd
61 6276 0 0x00BB 3659611 CXPACKET 5 9 184826204 114737 2 35:53.8 35:53.8 0 2 suspended INSERT
61 6540 0 0x0000 0 SOS_SCHEDULER_YIELD 5 9 3503094 513 0 35:53.8 35:53.8 2 0 runnable INSERT
61 360 0 0x0000 0 SOS_SCHEDULER_YIELD 5 9 3377297 420 0 35:53.8 35:53.8 4 0 runnable INSERT
61 4348 0 0x0000 0 SOS_SCHEDULER_YIELD 5 9 3446657 515 0 35:53.8 35:53.8 3 0 runnable INSERT
61 5532 0 0x0000 0 SOS_SCHEDULER_YIELD 5 9 3094360 443 0 35:53.8 35:53.8 5 0 runnable INSERT
I suspect the query is going parallel and blocking itself, as all of the activity is occuring on the same spid. but I'm at a loss as to how to troubleshoot further.
any thoughts on what is happening here? or what other steps i could take to troubleshoot this if it occurs again?
I'm looking for the syntax to setup windows server core R2 to take its proxy configuration from a script(.pac file)
for example in my LAN settings dialog:
Automatic configuration
use automatic configuration script(checked)
address http://foo.bar/proxy.pac (text box)
any thoughts on how I can set this netsh doesn't appear to support this unless I'm missing something.
I was told by our DNS administrator that the use of CNAME records was not "best Practice" and was a security vulnerability. is this true? I have always used CNAME records to reduce the management overhead of DNS records.
In the past, I have used contig.exe to remove physical fragmentation from SQL Server data files. They have always been on locally attached storage. Is there any benefit to running this on a data file that is stored on a SAN?
We have a dataload job that moves a relatively large amount of data across the network between two sql servers. the servers are on the same subnet and there is only a switch between them. the data consists of several large varchar fields plus an xml field.
In order to increase throughput. I have tried changing the network packet size from the default 4096 to 32627 on the connection string; However it doesn't seem to be helping performance. I suspect the issue is that although we a running gig ethernet, "jumbo frames" are not enabled.
To confirm this, I tried two ping tests:
ping -l 1400 -f pdbsql01dul
Works
ping -l 4096 -f pdbsql01dul
Packet needs to be fragmented but DF set.
as you can see the largest packet size appears to be around 1400
My question is, if Jumbo frames are ~8096, is there any benefit of setting the network packet size larger than that?
Does this change if the connection is local to the server in question?