Some basic levels in Perimeter Protection

 

A basic home office setup with the following components can definitely offer a decent level of protection against Phishing.

 

1. A Chromium based Web Browser
2. AVG Antivirus
3. Cisco Umbrella OpenDNS

 

A sample URL picked up Phishtank to test the same.

 

Opera (Chromium based Browser) presents a recommendation not to visit the URL. (Override-able by the user)

 

 

TCP level protection by Web Shield component of AVG Antivirus (not override-able by the user without confirmation using administrative privileges)

If a link escapes these two protection by any chance, Cisco Umbrella to have its sway (not override-able by the user without confirmation using administrative privileges)

JSON Standard for Resume

Innovations can never be stifled. And one innovation and its implementation always seeds another. We have been having our profiles (aka) Curriculum Vitae (aka) Resume in notepad text files a few years ago and then moved onto Word and PDF format files for rich presentation.

Then came video profiles which were more commonly used by media personnel.

Having seen a diverse set of formats to present the profiles the new trend now is an open standards for resume based on JSON You can find more details about it from here and can contribute your technical excellence and/or feedback here.

A simple .JSON resume as a public gist at https://gist.github.com/ can be used as an input to the parser hosted by JSON resume which supports a lot of themes to publish as a profile website.

For example this blogger has their JSON resume here.

 

Switching SQL Server between Multi-User and Single User mode with a simple T-SQL

Recently had to manage database deployments where the SQL Server was hosted with a cloud solution provider of repute. The database was quite huge and hence during backup and restore had to switch the same to Single User mode. However the database was so huge that even after service refresh the right click properties on the database was not able to open because of resource contingency.

Hence I chose to have this switch done through simple T-SQL which I would like to share the same here for everyone’s benefit.

To Switch to Single User Mode:

use master
go
alter database [YourDatabaseName] set single_user with rollback immediate

 

To Return Back to Normal/Multi-User Mode:

use master
go
alter database [YourDatabaseName] set single_user with rollback immediate

Additionally there is one more argument called WITH NOWAIT which could be used if needed