I suggest to have regular full backup of your system database along with user database. But if you do not have system database & your MSDB got corrupted then you have to rebuild it. You can do it by instmsdb.sql script comes with installation. It will result in loss of SQL Agent jobs, backup & restore history, database mail configuration etc. Let’s have a demo for that :-

1. Stop all services connecting to the Database Engine, including SQL Server Agent, SSRS, SSIS, and all applications using SQL Server

The WordPress.com stats helper monkeys prepared a 2014 annual report for this blog.

Here’s an excerpt:

The Louvre Museum has 8.5 million visitors per year. This blog was viewed about 73,000 times in 2014. If it were an exhibit at the Louvre Museum, it would take about 3 days for that many people to see it.

The 5th cumulative update release for SQL Server 2014 RTM is now available for download at the Microsoft Support site. Cumulative Update 5 contains all the hotfixes released since the initial release of SQL Server 2014 RTM.

Those who are facing severe issues with their environment, they can plan to test CU5 in test environment & then move to Production after satisfactory results.

To other, I suggest to wait for SP1 final release to deploy on your production environment, to have consolidate build.

Today, My one of friend come back from SQL DBA interview & share his review. One question about which he is looking for was “What is the use of RPC in cluster” ?

The Remote Procedure Call (RPC) [http://support.microsoft.com/kb/832017] system service is an interprocess communication (IPC) mechanism that enables data exchange and invocation of functionality that is located in a different process. The different process can be on the same computer, on the LAN, or in a remote location, and it can be accessed over a WAN connection or over a VPN connection. The RPC service serves as the RPC Endpoint Mapper and Component Object Model (COM) Service Control Manager. Many services depend on the RPC service to start successfully. RPC did not use fixed ports, it worked on port ranges. RPC also works on Named pipe for “File and Printer Sharing” services.

Windows Cluster use multiple port (at least 100 ports) for different process via RPC. This process can be available over same system, depended system, over LAN or WAN, Domain Controller etc. RPC works on range of ports instead of fix port. This feature of RPC makes it very useful. Sometime critical ports can be already in user by some other process at that time RPC can use other ports from available range for connectivity.

There is long list of services that depends on RPC [http://technet.microsoft.com/en-us/library/cc787851(v=ws.10).aspx] like : Telnet, DHCP, DNS, COM+, DTC, WINS etc.

4) Your issue should be resolved now. If you still face same issue that means there are chances that you may be running with different versions of SQL Server. If yes, Please try to patch SQL Server Management Studio (SSMS) with latest available Service pack.