September 25, 2012 at 1:09 pm
Here is the bug demonstration in sql server 2008r2
a. Check the Server Collation : should be SQL_Latin1_General_CP1_CI_AS
b. Create a login: abcd
c. Create a database: someDb with collation: Latin1_General_CI_AS_KS_WS
d. Create a user: abcd in database someDb and map it to login abcd
e. Now open properties of login “abcd”.
f. First open “User Mappings”.
g. Now open “Securables”, you will get error exception.
Here is the discussion:
This is a bug in sql server 2008 r2 I'm facing now. It should have a fix available for this. Can anyone tell me with which service pack is this covered? or how to overpass this.
Thanks
IgorMi
Igor Micev,My blog: www.igormicev.com
September 25, 2012 at 2:13 pm
I'd go straight to Microsoft on this one, if Bing/Google/whatever doesn't pull something useful up straight off the error message.
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
September 25, 2012 at 2:49 pm
Hi GSquared,
Yes sure, if it was for a production I'd have gone with microsoft directly. This is, fortunately, not a problem on productions as their databases have same collation as the server instance. I do restores from more productions on a test server , and the backups are coming with different collations. Moreover the test server is a virtual machine. I cannot make a system restore. I'll probably try with latest cumulative hotfixes for sql server 2008r2.
Additionally, can someone tell me if this is resolved with sql server 2012 ?
Thanks
IgorMi
Igor Micev,My blog: www.igormicev.com
September 26, 2012 at 1:20 pm
Hi All,
If somebody was interested in this issue, I can contribute to it after experiencing on. After being searching the net for the concrete fix for the issue and finishing unsuccessfully, I downloaded the following cumulative fix: SQLServer2008R2-KB2703280-x64 and installed it. The issue was resolved.
I also tried using a Login with different databases with different collations on an sql server 2005 instance and it worked there without any issues.
Regards
IgorMi
Igor Micev,My blog: www.igormicev.com
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply