|
Home > Archive > MS SQL Server > January 2006 > Re: Ident_insert behaiviour change in SSDS 2005 - MS, read please!
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Re: Ident_insert behaiviour change in SSDS 2005 - MS, read please!
|
|
| Koni Kogan 2006-01-26, 4:53 pm |
| Looks like it is more than just that function... Similar problem is with
object_id()... The plot thickens... Did I miss a BIG announcement?
Koni Kogan wrote:
> It looks like to get a correct value returned from IDENT_Current(‘Table
> name’ a user must have at least 'select' or 'insert' permission on the
> underlying table as opposed to just having an 'execute' permission for a
> stored procedure that uses the function in Sql2K. Is this simply a bug?
> I hope it is!
| |
| Koni Kogan 2006-01-31, 8:23 pm |
| Yes I did! Or may be it was not announced at all! But here is the
solution: change all you stored procs and triggers that use functions
that access any metadata in SSDS 2005 (object_id() and so on...). Or
your users that do not have permissions to see that metadata will get
NULLS returned instead of data. Read the following that explaines how
to get around the problem:
http://msdn2.microsoft.com/en-us/library/ms188354.aspx
I'd like to thank all MS experts in this group for timely help with
this... Hmm... Well may be this is a surprise for them too...
Koni Kogan wrote:
[color=darkred]
> Looks like it is more than just that function... Similar problem is with
> object_id()... The plot thickens... Did I miss a BIG announcement?
>
> Koni Kogan wrote:
>
|
|
|
|
|