What do we do?

Do you want someone to manage your SQL Server hassle free?
Do you have interest in SQL Server?
Do you require a trainer?
Do you require someone to troubleshoot your system?

If you have lots of questions like this come to us. SQL-Articles team has a well experienced SQL Server professionals who can take care of all your requests related to SQL Server.

What do we provide?

  • We provide corporate training on SQL Server of any version
  • We will mentor you to learn SQL Server in a better way. If you are Interested in SQL Server come to us , we will teach you
  • Remote DBA Services, provides SQL server support round the clock
  • Performance Tuning & Optimization
  • Migrating to SQL Server
  • Upgrading to SQL Server
  • Auditing SQL Server

To get a quote drop an email to consulting@sql-articles.com, our experts will get back to you.

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