April event is the second SQL Server user group meet in this year. As you all know Mr. Pinal Dave has stepped into our meet this time and its nice to meet him after Teched. We planned to start it by 9.30 AM however we could see some of the participants already reached the venue by 9 AM itself, appreciate their interest in learning things. The day has started somewhat ok because you know power cut happened on the entire Chennai and we couldnt get any other conference hall at that time. Venkat has jumped with his office colleagues and he managed to get a generator with in 45 min, which I wanted to really appreciate him and all the efforts he has taken to bring the power back. Thanks Venkat.
VN:F [1.9.17_1161]
Rating: 2.3/5 (3 votes cast)
VN:F [1.9.17_1161]
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. [...]