Many of us are data professionals, and we might have no idea how much data a user can access using today's modern mobile devices. Potentially we can help them understand that the $500 smartphone they use can actually contain and access much more than $500 worth of data. If their device is the cause of a data breach, the cost could easily be much closer to $50,000 than $500.
Security is always a big gamble, and rather than the old models of controlling all devices and limiting access, we need to learn to educate users, work with them to secure their devices and report losses quickly. The survey shows that most employees don't even know how to report the loss of a device that might cause a data breach. At the very least, we can establish some procedures that will allow an account to be quickly turned off. And to ensure productivity doesn't suffer, we need a procedure that also engages a new account for a user quickly.
My guess is a lot of security issues could be handled quicker if we ensured that users were aware of issues and penalized for ignoring them, but made sure those penalties were balanced with an understanding that there it is inevitable people will make mistakes and accidents. Forgive mistakes and ask for reports of potential issues quickly.
Free ebook "TortoiseSVN and Subversion Cookbook - Oracle Edition"
Use these recipes to work better, faster, and do things you never knew you could do with SVN. If you're new to source control, this book provides a concise guide to getting the most out of Subversion. Download it free
5 ways to code effortlessly
Discover the different ways you can make writing, exploring, and refactoring SQL code refreshingly effortless with SQL Prompt 6. Download a free trial.
Load tests give the database administrator quite a lot of valuable information and may make the difference between poor and acceptable application performance. But are there any gotchas or traps associated with big data? More »
SQL Server 2012 brought in some great new features and one of the important ones is scalability and performance via AlwaysOn. AlwaysOn is a superset feature and is a combination of many things you will learn about. As the language suggests, this technology achieves a SQL Server infrastructure that can be "always on". For businesses that run 24x7 downtime means the loss of business. This type of risk is out of the question for these businesses. This book discusses in detail the concepts of SQL Server AlwaysOn starting from the basics.
Yesterday's Question of the Day
(by free mascot):
Is it possible to create more than 1 distribution database for replication on a SQL instance i.e. distribution, distribution1 etc. on SQL Server 2012?
You can do so by navigating on Management Studio of a server which is having distributor database:
1. Open Distributor properties... by right clicking replication folder.
2. Click on general tab > right pan you can see the Distribution Databases and Databases: you can find the distribution databases
3. Click New... icon to create new dristirbution database and click OK.
Here you go.. You have created another distribution1 database.
No users can Print SSRS reports
- They get Error loading resource library. (0x8007007E).
deleted rsclientprint*.* from windows/system and windows/
reinstalled to c:\windows\downloaded program files\
Still the same...
- After seeing this: [url]http://www.sqlservercentral.com/Forums/Topic1546354-391-1.aspx[/url]
I'd like to see some articles that look at real situations where you've replaced a cursor (or...
This newsletter was sent to you because you signed up at SQLServerCentral.com.
Feel free to forward this to any colleagues that you think might be interested.
If you have received this email from a colleague, you can register to receive it here.