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.

Recent Posts

Recent Comments

RA

|

Thanks for the script. I had database with space between the names.

I modified to use square brackets:

FROM [?].sys.database_principals a
LEFT OUTER JOIN [?].sys.database_role_members

and

from [?].sys.database_permissions join [?].sys.sysusers U
on grantee_principal_id = uid join [?].sys.sysobjects

Gangadhar NG

|

This tip is helpful enough for me.
thanks.

Zukunftsmusik

|

Thanks! That helped my a lot. But there’s a little mistake:
SQL_Latin1_General_CP1_CI_AS stands for “Latin1-General, case-insensitive, accent-sensitive [...]” therefore sort order 52.

If you want to set the sort order to 54 the correct collation would be “SQL_Latin1_General_CP1_CI_AI” ;)

Amit Bhatt

|

Hi Deepak,

Thanks for such a nice article.

You missed one thing to add in code:
@article = ‘all’,

Hence the script will be like this:
EXEC sp_addsubscription
@publication = ‘mypublication’,
@article = ‘ALL’,
@subscriber = ‘Subscriberservername’,
@destination_db = ‘mydestinationdbname’,
@reserved=’Internal’

Error 18486 | Platformblog

|

[...] SQL-Articles » Troubleshooting Login failed Error 18456This is one of the infamous error message (and number) that most of the DBAs …. 18486. Login failed for user ‘%.*ls’ because the account is currently locked out. [...]

Rating