Search results for 'app:weblogs' matching tags 'SQL Server', 'security', and 'access'

SQL Server agent: Property pagersendsubjectonly is not available for alert system this property may not exist for this object or may not be retrievable due to insufficient access rights.

Anonymous — Wed, 05 Jan 2011 06:00:00 GMT

Do you see this error in your environment? Is it a frequently occuring issue? In the recent time in a 64 bit environment we started to get this alert generated and DBAs complaining sometimes are unable to view the SQLAgent jobs on that remote server. If we observe the error text it clearly states " ....this property may not exist for this object or may not be retrievable due to insufficient access rights ". The first part is property may not exist for this object which means a tools problem and to...(read more)

SQL Server 2008 Security gotcha: BUILTIN\Administrator is no longer SYSADMIN, only in case of?

Anonymous — Tue, 29 Jun 2010 05:00:00 GMT

Here is an interesting 'sql security' discussion I had during the SASSUG usergroup interaction with regard to BUILTIN\Administrator role from SQL Server 2008 onwards. Since SQL Server 2005 the instance has been classified as 'secured by design/default' by cutting down the elevated access to the SQL Server. From the operating system side login privilege, by default SQL adds the group BUILTIN\Administrators to the sysadmin fixed server role, meaning that any local NT administrator is automatically...(read more)

How to make unwanted access to SQL Server 2005 by an operating system administrator more difficult

Anonymous — Fri, 12 Oct 2007 05:00:00 GMT

The following pages were recently modified. Source: Knowledge Base Product: Microsoft SQL Server 2005 Enterprise Edition, SQL Server 2005 Standard Edition & SQL Server 2005 Enterprise X64 Edition Notification Contents: New and Major Modifications How to make unwanted access to SQL Server 2005 by an operating system administrator more difficult http://support.microsoft.com/kb/932881/en-US...(read more)

An error has occured while establishing a connection to the server. When connecting to SQL Server 2005,this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.(provider:Named Pipes ....)

Anonymous — Thu, 26 Jul 2007 05:00:00 GMT

Error: An error has occured while establishing a connection to the server. When connecting to SQL Server 2005,this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.(provider:Named Pipes Provider,error:40-Could not open connection to SQL Server)) You might have seen the above error very frequentily within your SQL 2005 environment, sometimes this will be frustating to find why it is not working when everything was working fine until last...(read more)

Restrict Access to SQL Server using "Certificates"

Anonymous — Mon, 02 Jul 2007 05:00:00 GMT

Within SQL Server 2005 you could take help of certificates to restrict the access from a particular client's machine. Few times (even me) confused with or get an impression that SSL encryption is same, for more information on SSL( Secure Sockets Layer) refer to KBA316898 in this case. There is much information available within SQL 2005 BOL in this case as compared to previous versions of SQL Server. On the question, SQL Server 2005 has capability to use SSL to encrypt data transmitted across the...(read more)