Home
Welcome to SQL-Articles
This website is totally dedicated to SQL SERVER, a specific implementation of a relational database server from MICROSOFT.SQL server has been in the industry for the past three decades and has come a long way from SQL 1.0, SQL 7.0 through to SQL SERVER 2012 aka SQL Server Denali. Number of voluntary and involuntary DBAs , developers working on SQL databases keep ticking every day and the main intent of this website is to help and educate each of those out in the field and new database professionals starting their venture with the SQL server.
SQL-ARTICLES host’s number of good articles related to various SQL server features and helpful T-SQL scripts. Apart from this, the readers and users can ask us anything about SQL server in our FORUMS column. We would like to maintain this website as a SQL server knowledge base and a technical information exchange point. Come in, have a look and drench yourself in the rain of SQL SERVER.
Matt Mason
| #
Great help. Thanks. I never thought to look in the event logs.
Lekss
| #
Hi FANOFHADR,
Yes , indeed you can use both the names ( primary and listener) to connect to the databases. But it makes more sense to include your listener name as data source in your connection string to make your apps listen to the current primary group of databases if a disaster has occurred.
If you are using your primary instance name in your connection string it means that everytime a failover occurs you need to update your connection string.
VidhyaSagar
| #
Thanks for the reply Mohamed
Mohamed Azlan
| #
Referring to my comment dated January 7, 2012 at 5:59pm
After struggling for so long i found a solution to this.
Before you reinstall SQL server using Mixed Mode Authentication. (I know the pain of doing that. Sometimes, it wont work for this because you backup your database.mdf under the non permissible user and when you attach it after reinstalling SQL it still shows the same 15247 error)
What worked for me is;
Logged in under windows authentication
1) Went to Database\Security -> Right clicked on my role -> Selected all the necessary permissions
2) Went to \Security ->Right clicked on my role -> Selected all the necessary permissions
3) Restart SQL
4) Log in using SQL authentication
5) Repeat steps (1) & (2)
By God’s grace it should work. If not, try reinstalling SQL with a positive mind
Mohamed Azlan
| #
Thank you for the very thorough troubleshooting guidelines you have provided in this website. Although my problem still remain unresolved I have picked up a tip or two from here.
Recently to deploy my site I changed my authentication from windows to SQL authentication. Successfully added the user to ‘Security\Logins’. But having problem enabling database role membership as it returns error 15247. I believe error 15151 is also that of permission issues.
If anyone have come across this problem before I really hope to get a few input to work around on this.
Thank you in advance.