Re: 302621 BulkAdmin permission

From: Dan Guzman (danguzman_at_nospam-earthlink.net)
Date: 07/31/04


Date: Sat, 31 Jul 2004 09:37:22 -0500

If your environment doesn't permit you to implement the workarounds
suggested in the article, consider using another technique such as DTS or
BCP.

-- 
Hope this helps.
Dan Guzman
SQL Server MVP
"Gary Billins" <gbillins@petvalu.com> wrote in message
news:727a01c4763a$502d66f0$a401280a@phx.gbl...
> What is the status of this SQL Server 2000 problem?
> I cannot find any fix for this problem.
>
> SYMPTOMS
> If a BULK INSERT command is issued by a user who
> Is part of the bulkadmin server role and has INSERT
> permissions to the table
> Is not part of the sysadmin, db_ddladmin, or db_owner role
> Is not the database owner
> The following error message is generated:
>
> Server: Msg 8104, Level 16, State 2, Line 1
> The current user is not the database or object owner of
> table '<table_name>'. Cannot perform SET operation.
> WORKAROUND
> To work around the problem, make sure that the user is
> also part of either the db_ddladmin or the db_owner
> database role in addition to the bulkadmin server role.
> Another workaround is to make the user the owner of the
> database.
>
> Thanks


Relevant Pages

  • Re: Stupid Database Tricks
    ... You are describing a possible workaround, ... Cascading updates can cause other problems, ... to have to handle a deadlock every time we touch the database. ... might end up rewriting history! ...
    (comp.databases.theory)
  • Re: SQLAgent error with job : The owner (domainSQLServerAdministratorUser) of job Optimizations Job
    ... The workaround is as you have found, to set the job owner to sa. ... Jasper Smith (SQL Server MVP) ... domain-controlers W2003 with AD. ...
    (microsoft.public.sqlserver.security)
  • Re: Found a bug - is it known? can others reproduce it?
    ... rises to 8.00.818 when the cumulative security patch MS03-31 has been ... applied to SQL Server 2000, service pack 3. ... a workaround might be preferable to waiting for a ...
    (microsoft.public.sqlserver.programming)
  • Re: Stupid Database Tricks
    ... some constraints are temporal, ... You are describing a possible workaround, ... issue is that if keys can be updated in a temporal database, ... introduce a system-generated surrogate that is guaranteed to never change ...
    (comp.databases.theory)
  • Re: Show History Does absolutely Bupkus
    ... you can workaround the problem by turning off the Timezones ... for the database. ...
    (microsoft.public.vstudio.sourcesafe)