Anhtq,
Well, your problem is solved. Deleting and readding a login, as well as
rebooting it, have had several opportunities to fix something that was not
quite right. It certainly is not a SQL Server caching issue (or at least I
am pretty certain that it is not), but domain to SQL Server changes may have
some caching latency depending on the version of SQL Server, Windows, your
domain controllers, etc, etc.
I would say that if the problem arises again, you could repost at that time.
RLF
"Anhtq" wrote in message
> Thanks for your answer.
>
> 1. BUILTIN\Administrators is in the group sysadmin. So I think it's not a
> problem of rights.
> 2. The function is a simple query, in which I'm sure that there isn't
> criteria on login.
>
> By the way, I've corrected this problem by:
> - Delete the login BUILTIN\Administrator from the list of login of
> database
> server.
> - Recreate this login
> (and of course some restart of server between whiles)
>
> I thought about problem of cache or something like that, but before
> carrying
> out these actions above, the clear of cache haven't had any effect.
>
> Someone has any idea ? >> Stay informed about: SQL Query return different result for different user