Skip to main content

Posts

Activity Monitor fails- Microsoft SQL Server Management Studio

Error Details: Getting below error when trying to open process details or checking long queries in Activity Monitor window in SQL server R2 Enterprise Edition. The Activity Monitor is unable to execute queries against server [xxxx server]. Activity Monitor for this instance will be placed into a paused state. Use the context menu in the overview pane to resume the Activity Monitor. Other Information: Unable to find SQL Server process ID [PID] on server [xxxx server] (Microsoft.SqlServer.Management.ResourceMonitoring) Solution : This error exist because one of your service is not enabled on server.Name of Service is Performance Counter DLL Host. Just go to Services in control panel and find service Performance Counter DLL Host set it automatic and start the service. After doing this you need to close sql and reopen again. If still error not resolved then go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\PerfProc\Performance by in registry editor using regedt32 command.

Virus protection tips for your laptop of PC

1. Please do not open any Email attachments from unknown sources your own personal mail accounts such as Yahoo, Gmail, etc. 2. Kindly take backup all your important Data regularly on CD or DVD and scan external disk before using. 3. Please  do not click on any Links , sent from unknown sources, either via Emails or accessing your Facebook,twitter account.  These can be infected with virus. 4. Please do not Disable your Anti-Virus under any circumstances on your machine. 5. Update all Patches - Antivirus, Operating System , MS Office and windows patches update . 6. If you are unable to open any of your files then need to check virus infection and scan with antivirus. 7. If you use or share any External Drives such as  USB Hard Disks, need to SCAN them with the Antivirus software before using them.

Disadvantages of materialized View in SQL

Following are the Disadvantages of materialized View in SQL 1.We can not perform any DML Operations on materialized View ,but you can perform DDL Operations like DROP.The thing is here it stores the all records even if it is duplicate or non-duplicates,especially which we are using aggregate values.For example daily loads,monthly loads,yearly loads.such cases it would be very helpful storing of entire data if it is new or old. The disadvantage is takes space Can only be based on a simple Select if you require real time data. maintaining the materialized View  Logs has an overhead on the master system. 2.We can't perform DML on materialized View  because it is like snapshot or read only .it is mainly used for reporting purposes.A materialized view can be either read-only, updatable or writable. We Can't Perform DML on read-only but can Perform DML on updatable or writable. 3.On readable - we cant perform DML. on updatable- we can perform DML, we need to create the mate

What is the Difference between count(*) and count(1) in SQL

Question: Following are the Differences between count(*) and count(1) in SQL Answer: 1.COUNT(*) will include NULLS but it counts no.of ROWS in a TABLE, AND COUNT(column_or_expression) counts no.of NOT NULL values within a COLUMN. 2.COUNT(*) is depend on full table but COUNT(1) is depend on only one column and both are given same output.

Difference between collection and bulk binding in SQL

Following at the Differences between collection and bulk binding in SQL To retrieve multiple rows we can use cursors or bulk collections. Cursors row by row mechanism so performance decreased. But collections not row by row process all rows retrieved at time so performance increased. And bulk bind means doing DML(data manipulation language) operations as a bulk. By using for all statement we can do bulk-binding. If you want to do bulk-bind first should use bulk collections .