You're welcome, Guogang,
It's not table owner that's required, but the sysadmin, db_owner or
db_ddladmin permission that is required. That will only be possible if you
give the authors these rights, but I suspect that you will not want to do
that as well, so "catch-22"....
An alternative, *might* be that you setup a schedule job task that does this
with the correct access rights, dbname & tablename and you provide some
means for the authors to request the running of this job.
Regards,
John
> Thanks for the information.
> But, I really want to let authors have the ability to rebuild the index,
so
> that their newly added content can be searchable immediately. But, due to
> security reason, they won't be logged in as owner of the table.
> Any suggestion how I can achieve the goal?
> Thanks again,
> Guogang
> > Guogang,
> > The most likely difference is one of permission, as you need sysadmin
> > permission level in order to execute sp_fulltext_table.
> > See SQL Server 2000 BOL title "sp_fulltext_table" - "Permissions
> > Only members of the sysadmin fixed server role, db_owner and db_ddladmin
> > fixed database roles, and the object owner can execute
sp_fulltext_table.
> "
> > FYI, you only need to post FTS related questions to the newsgroup:
> > microsoft.public.sqlserver.fulltext.
> > Regards,
> > John
> > > Hi,
> > > I want to run this within my sotred procedure:
> > > Such that an authorized user can connect to database, and run this
> stored
> > > procedure to initiate a rebuild of index.
> > > The problem is I get an exception in my C# code which calls this
stored
> > > procedure:
> > > System.Data.SqlClient.SqlException: User does not have permission to
> > perform
> > > this action.
> > > I can execute the following stored procedure in the same way without
any
> > > problem:
> > > EXEC SP_XML_PREPAREDOCUMENT
> > > So, what is the difference? Why am I getting an exception?
> > > Thanks,
> > > Guogang
by