Viewing 15 posts - 1 through 15 (of 190 total)
Thanks. Would such permissions pertain to the SQL Server Service Account?
August 22, 2018 at 5:33 pm
Yes
February 1, 2018 at 11:49 am
October 26, 2017 at 9:29 am
October 25, 2017 at 1:38 pm
Yes. We literally took a backup of the starting database from server A and restored it on server B. Execution plans are identical.
October 25, 2017 at 12:52 pm
September 7, 2017 at 1:51 pm
January 18, 2017 at 1:13 pm
Yeah, I tried restarted the endpoints. Didn't help.
July 21, 2016 at 8:45 am
Weird. I was using the namespace, but I might have had something wrong with the formatting. Just tried it again and it worked. Thanks!
June 15, 2016 at 3:49 pm
Problem solved. Was given the wrong stored proc to modify. Ugh.
October 19, 2015 at 11:42 am
It's inside a stored proc being called by EF.
October 19, 2015 at 11:32 am
Actually, it was a bonehead move on my part. I realized that I was joining to another table using a different column from the table involved in the key lookup....
September 15, 2015 at 2:19 pm
Is the only difference that yours is able to handle situations where Customer.CountyId has a record that isn't in County.CountyId? I have a non-nullable FK constraint between Customer and County,...
March 25, 2015 at 12:05 pm
Yep, that did it. Thanks!
March 25, 2015 at 11:18 am
Ah, interesting. I found another way to do it in the interim, but I think I like your approach better. Thanks!
March 9, 2015 at 11:36 am
Viewing 15 posts - 1 through 15 (of 190 total)