I have developed this utility to monitor the instances of SQL Server running in a machine (i.e only standalone and not remote machines) and to send failure mail alerts upon service status. When I tried this type of systray utility in internet I could find only utilities that are monitoring the service and not sending any alerts on failures, so Ive decided to add this feature in this. I hope this small utility could help you a lot.
You can create an object in SQL Server and convert it to a system object just by marking the object as given below. By doing so you will be able to call the procedure from any db context
I have planned to configure SQL Server 2008 clustering on Windows Server 2008 Clustering. To do this, first I need to configure Windows Server Clustering. Now a days DBA’s are not only working on RBMS platform, they should also have sufficient knowledge in their operating system on which their RDBMS is running. As a DBA we shouldn’t look into SQL Server cluster alone, we should also take part in windows clustering too. In this article Im going to configure failover clustering in Windows server 2008.
In this article we are going to take a look at the 5th system databases available right from SQL Server 2005. As everyone know till SQL Server 2000 there are four system database is available and they are master, model, msdb and tempdb databases. From SQL Server 2005 Microsoft has introduced a new system database to the database engine called Resource database (actual name for this database is mssqlsystemresource ) which is hidden to the users.
I recently received a call from one of my friend asking me, what is the easiest way to migrate a database from ACCESS to SQL Server? I was curious on answering his question and just went for a search in internet to find it was much simple than what I expected. This article describes the steps to migrate a Access database to SQL Server.