Browse by Tags

• access
• computing
• error
• high availability
• Integration
• login
• management
• named pipes
• not found
• performance
• property
• remote
• sql express
• SQL Server
• ssas
• ssis
• ssma
• ssrs
• surface
• tcp
• x64

• Property IsLocked is not available for Login '[x]'. This property may not exist for this object, or may not be retrievable due to insufficient access rights. (Microsoft.SqlServer.Smo)

  One of my colleague has been getting following error when trying to open few logins properties to change their default databases using SSMS. TITLE: Microsoft SQL Server Management Studio ------------------------------ Cannot show requested dialog. ------------------------------ Read More... Posted Wednesday, August 22, 2007 11:56 PM from SSQA.net | (Comments Off) Filed under: security, SQL Server, SSMS, error, login, property, ssma

• [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()). [ODBC SQL Server Driver][DBNETLIB]Specified SQL server not found

  --------------------------- Microsoft SQL Server Login --------------------------- Connection failed: SQLState: '01000' SQL Server Error: 11004 [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()). Connection failed: SQLState: '08001' Read More... Posted Wednesday, August 22, 2007 12:06 AM from SSQA.net | (Comments Off) Filed under: security, SQL Server, Integration, SSMS, error, high availability, surface, not found

• Whats with 64 bit computing on SQL Server

  What advantages we took when deployed the 64-bit computing within SQL Server As you aware 64 bit computing with 64-bit processors have become the standard for systems ranging from the most scalable servers to desktop PCs. The way to take full advantage Read More... Posted Sunday, August 05, 2007 12:41 AM from SSQA.net | (Comments Off) Filed under: security, SQL Server, performance, SSMS, x64, management, computing, ssis, ssrs, ssas

• 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 ....)

  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 Read More... Posted Thursday, July 26, 2007 10:49 PM from SSQA.net | (Comments Off) Filed under: security, SQL Server, performance, SSMS, tcp, sql express, error, access, named pipes, remote, management