I hope you have been through both Part 1 and Part 2 of this series .In Part 1 we discussed about using WMI based real-time alerts using SQL Server Agent and shared the example of capturing blocking through it .In Part 2, I shared with you how you can create several SQL Server related alerts on your own and did WMI Deadlock alert for you. In this part we will see how to capture OS related alerts.I will share an example of High CPU alert with you .Using the same example you can create different ot...
Read More
In the first part of this blog series, we discussed that starting with SQL Server 2005, we can use SQL Server agent to capture WMI based alerts.We can insert the alret data in to SQL Server tables and use it as needed .We took the example of Blocking and found how we can get all the information related to blocking without having the need to log on to the problematic SQL Server instance. In this part we will try to explore how to create more such alerts easily .We will only discuss about SQL Serv...
We all know that that SQL Server had a great face lift from SQL Server 2000 to 2005 .Everything else was a history after that .It was a big leap and we can count the new features of SQL Server 2005 on fingers. However there is one feature that I feel should have been marketed but was not done. Starting from SQL Server 2005, we can use SQL Server agent to capture WMI alerts .While this is catching up fast in the SQL Server community, many still do not know what magic this functionality can do and...
This is the last one in this series .While PART - 1 and PART – 2 were somehow correlated , this blog post is independent and has no dependency on the previous 2 parts .Nor does the previous 2 parts have any dependency on this post . In this post I will discuss about a coupel of settings that can help us improving replication performance .Be careful in selecting them for implementation in your environment and do thorough tests on staging /Dev servers first.By saying be carefule I did not me...
Hope you have liked the first part of fine tuning transactional replication. In case you have not been through it you can check it here . In this part we will talk about improving distribution agent throughput by modifying the profile parameters .it’s important to note that the changes that you make in the log reader agent might increase latency from distributor to subscriber if you leave the distribution agent unchanged .This is because if you increase the log reader throughput only, you ...
I remembered my childhood days when I use to get mechanical toys and how I use to experiment with them eventually ending up messing everything.This is true even when we grow old . Sometimes we commit bigger mistakes .Sometimes we do not take some good steps because we are scared in case something goes wrong. We DBAs are no saints and many a times try and experiment with the system without proper approach and in a haste to see the better results quickly (the intention is always good though). (SQL...
Hi Guys , A few days ago someone at client's site removed the builtin administrator from SQL Server as it was one of the risks mentioned in the agreement .Everything was fine and no one realized what mistake has been done. Things were fine till the time it was needed to login to SQL Server .No one saved SA password either and een though the SA login was enabled , we were not able to use it ....awesome ... They were about to uninstall and reinstall SQL server when we finally could resolve the iss...
Introduction We all know that data retrieval will be fast if the data pages are found in RAM .If the data pages are not in RAM, they are fetched into RAM from the disk. This causes a physical IO .The page remains in the RAM until it’s again kicked off to Disk. But the process and threads do not access the Physical memory (RAM) directly .Instead the RAM is accessed indirectly through Virtual Memory or Virtual address space (VAS) pointers. On a x86 operating system the number of such pointer...
While many of you might have tested and implemented the stored procedure execution already, many might still be considering it and surely would be Googling or Binging around to find the right solution. I have done some testing that might help you .For testing I have I have used instances of SQL Server 2005 SP3 (CU2) and SQL Server is 2008 SP1 . Background: Imagine a situation where your databases are in TBs or in hundreds of GBs and you are using transactional Replication without updatable subsc...
Hi Friends , Sometime back, there was a request on the MSDN forums where the OP wanted to archive the replicated partitioned tables in the publisher database . I think it would be good to share the solution with everyone in this forum as well .I have used SQL Server 2008 Evaluation Edition SP1 , Build 10.0.2531 for my testing . In this post we will see : Part 1) archiving the replicated non-partitioned (normal) tables . Part 2) archiving the replicated partitioned tables . At the end ,you will n...