About Brumedishetty

I work as a SQL Server DBA. Look at the About Me page for more info

It’s just a read only user right???

Should we be worried about a read only user? At first look, it looks like, “no we shouldn’t be worried” by a user who has only read access to a database. That is only partially true and on several occasions, I had to explain the people requesting such as access what potential danger, such a read-only user can cause. So I thought it might be a good blog post to publish.

Whenever you come across a read-only user, we assume we are good from the security perspective that it’s ok for this particular user to have a read permissions on the database and there is no harm as that user cannot make any changes to the underlying data. I agree to that statement, but from a point of view other than data security, we will have to recognize that there can be an impact on the performance of SQL Server, on which this database exists.

Consider the case if this read-only user credentials are used in an SSIS package to read a large chunk of data and pushed across to another data destination. When a large number of rows are read from the SQL Server database, that data is first brought into the buffer (memory) of the SQL Server, there by causing any data inside the buffer (that is being actively used) to be flushed off the memory. This might cause a huge impact on the other applications (that read/write to the dbs on this SQL Server). So always keep in mind about this whenever you are creating a read only user. Educate the user who is requesting the read only access about these potential performance impact and let them try to limit their result sets to as minimal as possible..

–Bru Medishetty

Do you like this site? Like our FB page @Facebook.com\LearnSQLWithBru so that, you know when there is a new blog post.

SQL Server 2014 released, get your evaluation copy

Starting today, April 1st (not a April fools joke), Microsoft has made available SQL Server 2014, the latest version of the database platform to the general public (aka RTM, Release to Market). You can go to this page — > Technet Evaluation Center to download your evaluation copy of SQL Server 2014. I am excited my self to see SQL Server 2014 in action personally. I finished downloading the eval copy and am looking forward to install it in a couple of days time. You can visit this page to get more information on SQL Server 2014..

Good luck !!!

— Bru Medishetty

Do you like this site? Like our FB page @ Facebook.com\LearnSQLWithBru so that, you know when there is a new blog post.

Cannot connect to a SQL Server 2008 named instance; How to resolve

Last month, I had this issue where a couple of applications had issues authenticating to a SQL Server 2008 R2 instance. So I started to troubleshoot this issue by duplicating from my workstation and finally arriving at a solution. This blog will explain what was caused this issue and the solution to that issue.

This SQL instance (that I had issues) is a 2008 R2 SQL Cluster and named instance, but it was configured to be accessible through the port 1433. So the SQL Instance was accessible both ways as (“clustername” and also as “clustername\instancename”). After a maintenance over a weekend (what is done on that cluster, what settings have been made and why is way out of topic in this blog), we started to have couple of applications not being able to authenticate to this SQL instance.  At first I could not think why this was happening, as I was able to see several users and applications connected to this instance and working fine (All SQL jobs running etc etc). I tried to login to that SQL instance (I commonly use just the clustername to connect) and was successful. Thought the individual accounts these applications are using to authenticate, have been disabled, but that was not the case, and lastly when I tried to login using the entire clustername\instancename then I found that I was having the same authentication failed error that those applications have been reporting. 


After looking at the state of SQL Services in SQL Server Configuration Manager, I found that the SQL Server Browser Service, though the Start Mode was set to Automatic, it did not start and was causing this issue. So I started the service and tried to login using the  clustername\instancename and it started to work…

SQL Server Browser

The above pic is how it looked on my server when I saw the services in configuration manager. (Note that this screen shot is from my lab not the actual server where this issue occurred).

Do you like this site? Like our FB page @ Facebook.com\LearnSQLWithBru so that, you know when there is a new blog post.

–Bru Medishetty