|
|
Posted by Dan Guzman on 09/20/05 15:39
As Erland mentioned, the bug hasn't yet been addressed. Your UDF
work-around is probably the best apporach.
May I ask why you need to use IDENT_CURRENT? The function has a global
scope so it needs to be used with caution in a multi-user environment.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"helmut woess" <hw@iis.at> wrote in message
news:1vrze3n4agi4u.1lx3hgebacr8k.dlg@40tude.net...
> Am Sun, 18 Sep 2005 17:58:46 GMT schrieb Dan Guzman:
>
>> http://support.microsoft.com/default.aspx?scid=kb;en-us;835188
>
> Hmmm, i am not sure what to do with this information. If it is a bug why
> was it not fixed in one of the next service packs?
> And there is no definition what the result will be after fixing the bug.
> And i did not find any information if this bug is fixed in SQL2005.
>
> In the meantime i wrote an UDF to check if the table is empty and then
> give
> me the right result. So it doesn't matter if Microsoft fixes the bug or
> not.
>
> but thanks for your information,
> Helmut
Navigation:
[Reply to this message]
|