Bulk Insert for non admins

Since Im pretty sure BCP is out, Ill look into Bulk Insert. I have a local
instance of SQL on my desktop. I create an SQL Login named BITest and allow
him into my Pubs DB. I then add him to the BulkAdmin fixed server role. When
I have him try to Bulk Insert, I get:
Server: Msg 8104, Level 16, State 2, Line 1
The current user is not the database or object owner of table
'pubs.dbo.t_access'. Cannot perform SET operation.
Which sort of indicates he needs to be in the db_owner role? Even though I
think thats crap, I add him to db_owner, and then try to run my Bulk Insert
again. This time I get:
Server: Msg 4834, Level 16, State 1, Line 1
You do not have permission to use the BULK INSERT statement.
So, not only does it really appear that he nees to be part of db_owner, it
still doesnt work. What gives?
TIA,
ChrisR
Chris,
From BOL:
Permissions
Only members of the sysadmin and bulkadmin fixed server roles can execute
BULK INSERT.
HTH
Jerry
"ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
news:8A4D0077-8989-4CA0-90AD-98EE96C9CEB8@.microsoft.com...
> Since Im pretty sure BCP is out, Ill look into Bulk Insert. I have a local
> instance of SQL on my desktop. I create an SQL Login named BITest and
> allow
> him into my Pubs DB. I then add him to the BulkAdmin fixed server role.
> When
> I have him try to Bulk Insert, I get:
> Server: Msg 8104, Level 16, State 2, Line 1
> The current user is not the database or object owner of table
> 'pubs.dbo.t_access'. Cannot perform SET operation.
> Which sort of indicates he needs to be in the db_owner role? Even though
> I
> think thats crap, I add him to db_owner, and then try to run my Bulk
> Insert
> again. This time I get:
> Server: Msg 4834, Level 16, State 1, Line 1
> You do not have permission to use the BULK INSERT statement.
> So, not only does it really appear that he nees to be part of db_owner, it
> still doesnt work. What gives?
> --
> TIA,
> ChrisR
|||Jerry, as indicated in my post, I added him to that role.
TIA,
ChrisR
"Jerry Spivey" wrote:

> Chris,
> From BOL:
> Permissions
> Only members of the sysadmin and bulkadmin fixed server roles can execute
> BULK INSERT.
> HTH
> Jerry
> "ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
> news:8A4D0077-8989-4CA0-90AD-98EE96C9CEB8@.microsoft.com...
>
>
|||Chris,
I got it to work with BULKADMIN and DB_OWNER. How many records to you have?
Do you really need to use BCP/BULK INSERT or would DTS possibly work?
HTH
Jerry
"ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
news:1B350D2E-A85B-4E25-B3C9-C19620DF0ACF@.microsoft.com...[vbcol=seagreen]
> Jerry, as indicated in my post, I added him to that role.
> --
> TIA,
> ChrisR
>
> "Jerry Spivey" wrote:
|||I have 48 reconds. DTS may work, but I'd really like to try to get this
going. You're user is NOT a member of either SA of Admins, right?
TIA,
ChrisR
"Jerry Spivey" wrote:

> Chris,
> I got it to work with BULKADMIN and DB_OWNER. How many records to you have?
> Do you really need to use BCP/BULK INSERT or would DTS possibly work?
> HTH
> Jerry
> "ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
> news:1B350D2E-A85B-4E25-B3C9-C19620DF0ACF@.microsoft.com...
>
>
|||I'd recommend DTS but it is your choice. No...created new login and user to
test for your example.
HTH
Jerry
"ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
news:63A4B6D4-EABD-409A-BD49-E39B0CC7FF6F@.microsoft.com...[vbcol=seagreen]
>I have 48 reconds. DTS may work, but I'd really like to try to get this
> going. You're user is NOT a member of either SA of Admins, right?
> --
> TIA,
> ChrisR
>
> "Jerry Spivey" wrote:
|||Curious, why DTS? Also, Im running SQL2K, and you?
TIA,
ChrisR
"Jerry Spivey" wrote:

> I'd recommend DTS but it is your choice. No...created new login and user to
> test for your example.
> HTH
> Jerry
> "ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
> news:63A4B6D4-EABD-409A-BD49-E39B0CC7FF6F@.microsoft.com...
>
>
|||Its fast, friendly (permissions issue in your case) and more functional.
SQL 2000 as well.
HTH
Jerry
"ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
news:B4925F9E-6BBB-477E-B4B7-9817D10CB89B@.microsoft.com...[vbcol=seagreen]
> Curious, why DTS? Also, Im running SQL2K, and you?
> --
> TIA,
> ChrisR
>
> "Jerry Spivey" wrote:

Bulk Insert for non admins

Since Im pretty sure BCP is out, Ill look into Bulk Insert. I have a local
instance of SQL on my desktop. I create an SQL Login named BITest and allow
him into my Pubs DB. I then add him to the BulkAdmin fixed server role. Whe
n
I have him try to Bulk Insert, I get:
Server: Msg 8104, Level 16, State 2, Line 1
The current user is not the database or object owner of table
'pubs.dbo.t_access'. Cannot perform SET operation.
Which sort of indicates he needs to be in the db_owner role? Even though I
think thats crap, I add him to db_owner, and then try to run my Bulk Insert
again. This time I get:
Server: Msg 4834, Level 16, State 1, Line 1
You do not have permission to use the BULK INSERT statement.
So, not only does it really appear that he nees to be part of db_owner, it
still doesnt work. What gives?
TIA,
ChrisRChris,
From BOL:
Permissions
Only members of the sysadmin and bulkadmin fixed server roles can execute
BULK INSERT.
HTH
Jerry
"ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
news:8A4D0077-8989-4CA0-90AD-98EE96C9CEB8@.microsoft.com...
> Since Im pretty sure BCP is out, Ill look into Bulk Insert. I have a local
> instance of SQL on my desktop. I create an SQL Login named BITest and
> allow
> him into my Pubs DB. I then add him to the BulkAdmin fixed server role.
> When
> I have him try to Bulk Insert, I get:
> Server: Msg 8104, Level 16, State 2, Line 1
> The current user is not the database or object owner of table
> 'pubs.dbo.t_access'. Cannot perform SET operation.
> Which sort of indicates he needs to be in the db_owner role? Even though
> I
> think thats crap, I add him to db_owner, and then try to run my Bulk
> Insert
> again. This time I get:
> Server: Msg 4834, Level 16, State 1, Line 1
> You do not have permission to use the BULK INSERT statement.
> So, not only does it really appear that he nees to be part of db_owner, it
> still doesnt work. What gives?
> --
> TIA,
> ChrisR|||Jerry, as indicated in my post, I added him to that role.
--
TIA,
ChrisR
"Jerry Spivey" wrote:

> Chris,
> From BOL:
> Permissions
> Only members of the sysadmin and bulkadmin fixed server roles can execute
> BULK INSERT.
> HTH
> Jerry
> "ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
> news:8A4D0077-8989-4CA0-90AD-98EE96C9CEB8@.microsoft.com...
>
>|||Chris,
I got it to work with BULKADMIN and DB_OWNER. How many records to you have?
Do you really need to use BCP/BULK INSERT or would DTS possibly work?
HTH
Jerry
"ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
news:1B350D2E-A85B-4E25-B3C9-C19620DF0ACF@.microsoft.com...[vbcol=seagreen]
> Jerry, as indicated in my post, I added him to that role.
> --
> TIA,
> ChrisR
>
> "Jerry Spivey" wrote:
>|||I have 48 reconds. DTS may work, but I'd really like to try to get this
going. You're user is NOT a member of either SA of Admins, right?
--
TIA,
ChrisR
"Jerry Spivey" wrote:

> Chris,
> I got it to work with BULKADMIN and DB_OWNER. How many records to you hav
e?
> Do you really need to use BCP/BULK INSERT or would DTS possibly work?
> HTH
> Jerry
> "ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
> news:1B350D2E-A85B-4E25-B3C9-C19620DF0ACF@.microsoft.com...
>
>|||I'd recommend DTS but it is your choice. No...created new login and user to
test for your example.
HTH
Jerry
"ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
news:63A4B6D4-EABD-409A-BD49-E39B0CC7FF6F@.microsoft.com...[vbcol=seagreen]
>I have 48 reconds. DTS may work, but I'd really like to try to get this
> going. You're user is NOT a member of either SA of Admins, right?
> --
> TIA,
> ChrisR
>
> "Jerry Spivey" wrote:
>|||Curious, why DTS? Also, Im running SQL2K, and you?
--
TIA,
ChrisR
"Jerry Spivey" wrote:

> I'd recommend DTS but it is your choice. No...created new login and user
to
> test for your example.
> HTH
> Jerry
> "ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
> news:63A4B6D4-EABD-409A-BD49-E39B0CC7FF6F@.microsoft.com...
>
>|||Its fast, friendly (permissions issue in your case) and more functional.
SQL 2000 as well.
HTH
Jerry
"ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
news:B4925F9E-6BBB-477E-B4B7-9817D10CB89B@.microsoft.com...[vbcol=seagreen]
> Curious, why DTS? Also, Im running SQL2K, and you?
> --
> TIA,
> ChrisR
>
> "Jerry Spivey" wrote:
>

Bulk Insert for non admins

Since Im pretty sure BCP is out, Ill look into Bulk Insert. I have a local
instance of SQL on my desktop. I create an SQL Login named BITest and allow
him into my Pubs DB. I then add him to the BulkAdmin fixed server role. When
I have him try to Bulk Insert, I get:
Server: Msg 8104, Level 16, State 2, Line 1
The current user is not the database or object owner of table
'pubs.dbo.t_access'. Cannot perform SET operation.
Which sort of indicates he needs to be in the db_owner role? Even though I
think thats crap, I add him to db_owner, and then try to run my Bulk Insert
again. This time I get:
Server: Msg 4834, Level 16, State 1, Line 1
You do not have permission to use the BULK INSERT statement.
So, not only does it really appear that he nees to be part of db_owner, it
still doesnt work. What gives?
--
TIA,
ChrisRChris,
From BOL:
Permissions
Only members of the sysadmin and bulkadmin fixed server roles can execute
BULK INSERT.
HTH
Jerry
"ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
news:8A4D0077-8989-4CA0-90AD-98EE96C9CEB8@.microsoft.com...
> Since Im pretty sure BCP is out, Ill look into Bulk Insert. I have a local
> instance of SQL on my desktop. I create an SQL Login named BITest and
> allow
> him into my Pubs DB. I then add him to the BulkAdmin fixed server role.
> When
> I have him try to Bulk Insert, I get:
> Server: Msg 8104, Level 16, State 2, Line 1
> The current user is not the database or object owner of table
> 'pubs.dbo.t_access'. Cannot perform SET operation.
> Which sort of indicates he needs to be in the db_owner role? Even though
> I
> think thats crap, I add him to db_owner, and then try to run my Bulk
> Insert
> again. This time I get:
> Server: Msg 4834, Level 16, State 1, Line 1
> You do not have permission to use the BULK INSERT statement.
> So, not only does it really appear that he nees to be part of db_owner, it
> still doesnt work. What gives?
> --
> TIA,
> ChrisR|||Jerry, as indicated in my post, I added him to that role.
--
TIA,
ChrisR
"Jerry Spivey" wrote:
> Chris,
> From BOL:
> Permissions
> Only members of the sysadmin and bulkadmin fixed server roles can execute
> BULK INSERT.
> HTH
> Jerry
> "ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
> news:8A4D0077-8989-4CA0-90AD-98EE96C9CEB8@.microsoft.com...
> > Since Im pretty sure BCP is out, Ill look into Bulk Insert. I have a local
> > instance of SQL on my desktop. I create an SQL Login named BITest and
> > allow
> > him into my Pubs DB. I then add him to the BulkAdmin fixed server role.
> > When
> > I have him try to Bulk Insert, I get:
> >
> > Server: Msg 8104, Level 16, State 2, Line 1
> > The current user is not the database or object owner of table
> > 'pubs.dbo.t_access'. Cannot perform SET operation.
> >
> > Which sort of indicates he needs to be in the db_owner role? Even though
> > I
> > think thats crap, I add him to db_owner, and then try to run my Bulk
> > Insert
> > again. This time I get:
> >
> > Server: Msg 4834, Level 16, State 1, Line 1
> > You do not have permission to use the BULK INSERT statement.
> >
> > So, not only does it really appear that he nees to be part of db_owner, it
> > still doesnt work. What gives?
> >
> > --
> > TIA,
> > ChrisR
>
>|||Chris,
I got it to work with BULKADMIN and DB_OWNER. How many records to you have?
Do you really need to use BCP/BULK INSERT or would DTS possibly work?
HTH
Jerry
"ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
news:1B350D2E-A85B-4E25-B3C9-C19620DF0ACF@.microsoft.com...
> Jerry, as indicated in my post, I added him to that role.
> --
> TIA,
> ChrisR
>
> "Jerry Spivey" wrote:
>> Chris,
>> From BOL:
>> Permissions
>> Only members of the sysadmin and bulkadmin fixed server roles can execute
>> BULK INSERT.
>> HTH
>> Jerry
>> "ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
>> news:8A4D0077-8989-4CA0-90AD-98EE96C9CEB8@.microsoft.com...
>> > Since Im pretty sure BCP is out, Ill look into Bulk Insert. I have a
>> > local
>> > instance of SQL on my desktop. I create an SQL Login named BITest and
>> > allow
>> > him into my Pubs DB. I then add him to the BulkAdmin fixed server
>> > role.
>> > When
>> > I have him try to Bulk Insert, I get:
>> >
>> > Server: Msg 8104, Level 16, State 2, Line 1
>> > The current user is not the database or object owner of table
>> > 'pubs.dbo.t_access'. Cannot perform SET operation.
>> >
>> > Which sort of indicates he needs to be in the db_owner role? Even
>> > though
>> > I
>> > think thats crap, I add him to db_owner, and then try to run my Bulk
>> > Insert
>> > again. This time I get:
>> >
>> > Server: Msg 4834, Level 16, State 1, Line 1
>> > You do not have permission to use the BULK INSERT statement.
>> >
>> > So, not only does it really appear that he nees to be part of db_owner,
>> > it
>> > still doesnt work. What gives?
>> >
>> > --
>> > TIA,
>> > ChrisR
>>|||I have 48 reconds. DTS may work, but I'd really like to try to get this
going. You're user is NOT a member of either SA of Admins, right?
--
TIA,
ChrisR
"Jerry Spivey" wrote:
> Chris,
> I got it to work with BULKADMIN and DB_OWNER. How many records to you have?
> Do you really need to use BCP/BULK INSERT or would DTS possibly work?
> HTH
> Jerry
> "ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
> news:1B350D2E-A85B-4E25-B3C9-C19620DF0ACF@.microsoft.com...
> > Jerry, as indicated in my post, I added him to that role.
> > --
> > TIA,
> > ChrisR
> >
> >
> > "Jerry Spivey" wrote:
> >
> >> Chris,
> >>
> >> From BOL:
> >>
> >> Permissions
> >> Only members of the sysadmin and bulkadmin fixed server roles can execute
> >> BULK INSERT.
> >>
> >> HTH
> >>
> >> Jerry
> >>
> >> "ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
> >> news:8A4D0077-8989-4CA0-90AD-98EE96C9CEB8@.microsoft.com...
> >> > Since Im pretty sure BCP is out, Ill look into Bulk Insert. I have a
> >> > local
> >> > instance of SQL on my desktop. I create an SQL Login named BITest and
> >> > allow
> >> > him into my Pubs DB. I then add him to the BulkAdmin fixed server
> >> > role.
> >> > When
> >> > I have him try to Bulk Insert, I get:
> >> >
> >> > Server: Msg 8104, Level 16, State 2, Line 1
> >> > The current user is not the database or object owner of table
> >> > 'pubs.dbo.t_access'. Cannot perform SET operation.
> >> >
> >> > Which sort of indicates he needs to be in the db_owner role? Even
> >> > though
> >> > I
> >> > think thats crap, I add him to db_owner, and then try to run my Bulk
> >> > Insert
> >> > again. This time I get:
> >> >
> >> > Server: Msg 4834, Level 16, State 1, Line 1
> >> > You do not have permission to use the BULK INSERT statement.
> >> >
> >> > So, not only does it really appear that he nees to be part of db_owner,
> >> > it
> >> > still doesnt work. What gives?
> >> >
> >> > --
> >> > TIA,
> >> > ChrisR
> >>
> >>
> >>
>
>|||I'd recommend DTS but it is your choice. No...created new login and user to
test for your example.
HTH
Jerry
"ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
news:63A4B6D4-EABD-409A-BD49-E39B0CC7FF6F@.microsoft.com...
>I have 48 reconds. DTS may work, but I'd really like to try to get this
> going. You're user is NOT a member of either SA of Admins, right?
> --
> TIA,
> ChrisR
>
> "Jerry Spivey" wrote:
>> Chris,
>> I got it to work with BULKADMIN and DB_OWNER. How many records to you
>> have?
>> Do you really need to use BCP/BULK INSERT or would DTS possibly work?
>> HTH
>> Jerry
>> "ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
>> news:1B350D2E-A85B-4E25-B3C9-C19620DF0ACF@.microsoft.com...
>> > Jerry, as indicated in my post, I added him to that role.
>> > --
>> > TIA,
>> > ChrisR
>> >
>> >
>> > "Jerry Spivey" wrote:
>> >
>> >> Chris,
>> >>
>> >> From BOL:
>> >>
>> >> Permissions
>> >> Only members of the sysadmin and bulkadmin fixed server roles can
>> >> execute
>> >> BULK INSERT.
>> >>
>> >> HTH
>> >>
>> >> Jerry
>> >>
>> >> "ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
>> >> news:8A4D0077-8989-4CA0-90AD-98EE96C9CEB8@.microsoft.com...
>> >> > Since Im pretty sure BCP is out, Ill look into Bulk Insert. I have a
>> >> > local
>> >> > instance of SQL on my desktop. I create an SQL Login named BITest
>> >> > and
>> >> > allow
>> >> > him into my Pubs DB. I then add him to the BulkAdmin fixed server
>> >> > role.
>> >> > When
>> >> > I have him try to Bulk Insert, I get:
>> >> >
>> >> > Server: Msg 8104, Level 16, State 2, Line 1
>> >> > The current user is not the database or object owner of table
>> >> > 'pubs.dbo.t_access'. Cannot perform SET operation.
>> >> >
>> >> > Which sort of indicates he needs to be in the db_owner role? Even
>> >> > though
>> >> > I
>> >> > think thats crap, I add him to db_owner, and then try to run my Bulk
>> >> > Insert
>> >> > again. This time I get:
>> >> >
>> >> > Server: Msg 4834, Level 16, State 1, Line 1
>> >> > You do not have permission to use the BULK INSERT statement.
>> >> >
>> >> > So, not only does it really appear that he nees to be part of
>> >> > db_owner,
>> >> > it
>> >> > still doesnt work. What gives?
>> >> >
>> >> > --
>> >> > TIA,
>> >> > ChrisR
>> >>
>> >>
>> >>
>>|||Curious, why DTS? Also, Im running SQL2K, and you?
--
TIA,
ChrisR
"Jerry Spivey" wrote:
> I'd recommend DTS but it is your choice. No...created new login and user to
> test for your example.
> HTH
> Jerry
> "ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
> news:63A4B6D4-EABD-409A-BD49-E39B0CC7FF6F@.microsoft.com...
> >I have 48 reconds. DTS may work, but I'd really like to try to get this
> > going. You're user is NOT a member of either SA of Admins, right?
> > --
> > TIA,
> > ChrisR
> >
> >
> > "Jerry Spivey" wrote:
> >
> >> Chris,
> >>
> >> I got it to work with BULKADMIN and DB_OWNER. How many records to you
> >> have?
> >> Do you really need to use BCP/BULK INSERT or would DTS possibly work?
> >>
> >> HTH
> >>
> >> Jerry
> >> "ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
> >> news:1B350D2E-A85B-4E25-B3C9-C19620DF0ACF@.microsoft.com...
> >> > Jerry, as indicated in my post, I added him to that role.
> >> > --
> >> > TIA,
> >> > ChrisR
> >> >
> >> >
> >> > "Jerry Spivey" wrote:
> >> >
> >> >> Chris,
> >> >>
> >> >> From BOL:
> >> >>
> >> >> Permissions
> >> >> Only members of the sysadmin and bulkadmin fixed server roles can
> >> >> execute
> >> >> BULK INSERT.
> >> >>
> >> >> HTH
> >> >>
> >> >> Jerry
> >> >>
> >> >> "ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
> >> >> news:8A4D0077-8989-4CA0-90AD-98EE96C9CEB8@.microsoft.com...
> >> >> > Since Im pretty sure BCP is out, Ill look into Bulk Insert. I have a
> >> >> > local
> >> >> > instance of SQL on my desktop. I create an SQL Login named BITest
> >> >> > and
> >> >> > allow
> >> >> > him into my Pubs DB. I then add him to the BulkAdmin fixed server
> >> >> > role.
> >> >> > When
> >> >> > I have him try to Bulk Insert, I get:
> >> >> >
> >> >> > Server: Msg 8104, Level 16, State 2, Line 1
> >> >> > The current user is not the database or object owner of table
> >> >> > 'pubs.dbo.t_access'. Cannot perform SET operation.
> >> >> >
> >> >> > Which sort of indicates he needs to be in the db_owner role? Even
> >> >> > though
> >> >> > I
> >> >> > think thats crap, I add him to db_owner, and then try to run my Bulk
> >> >> > Insert
> >> >> > again. This time I get:
> >> >> >
> >> >> > Server: Msg 4834, Level 16, State 1, Line 1
> >> >> > You do not have permission to use the BULK INSERT statement.
> >> >> >
> >> >> > So, not only does it really appear that he nees to be part of
> >> >> > db_owner,
> >> >> > it
> >> >> > still doesnt work. What gives?
> >> >> >
> >> >> > --
> >> >> > TIA,
> >> >> > ChrisR
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>|||Its fast, friendly (permissions issue in your case) and more functional.
SQL 2000 as well.
HTH
Jerry
"ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
news:B4925F9E-6BBB-477E-B4B7-9817D10CB89B@.microsoft.com...
> Curious, why DTS? Also, Im running SQL2K, and you?
> --
> TIA,
> ChrisR
>
> "Jerry Spivey" wrote:
>> I'd recommend DTS but it is your choice. No...created new login and user
>> to
>> test for your example.
>> HTH
>> Jerry
>> "ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
>> news:63A4B6D4-EABD-409A-BD49-E39B0CC7FF6F@.microsoft.com...
>> >I have 48 reconds. DTS may work, but I'd really like to try to get this
>> > going. You're user is NOT a member of either SA of Admins, right?
>> > --
>> > TIA,
>> > ChrisR
>> >
>> >
>> > "Jerry Spivey" wrote:
>> >
>> >> Chris,
>> >>
>> >> I got it to work with BULKADMIN and DB_OWNER. How many records to you
>> >> have?
>> >> Do you really need to use BCP/BULK INSERT or would DTS possibly work?
>> >>
>> >> HTH
>> >>
>> >> Jerry
>> >> "ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
>> >> news:1B350D2E-A85B-4E25-B3C9-C19620DF0ACF@.microsoft.com...
>> >> > Jerry, as indicated in my post, I added him to that role.
>> >> > --
>> >> > TIA,
>> >> > ChrisR
>> >> >
>> >> >
>> >> > "Jerry Spivey" wrote:
>> >> >
>> >> >> Chris,
>> >> >>
>> >> >> From BOL:
>> >> >>
>> >> >> Permissions
>> >> >> Only members of the sysadmin and bulkadmin fixed server roles can
>> >> >> execute
>> >> >> BULK INSERT.
>> >> >>
>> >> >> HTH
>> >> >>
>> >> >> Jerry
>> >> >>
>> >> >> "ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
>> >> >> news:8A4D0077-8989-4CA0-90AD-98EE96C9CEB8@.microsoft.com...
>> >> >> > Since Im pretty sure BCP is out, Ill look into Bulk Insert. I
>> >> >> > have a
>> >> >> > local
>> >> >> > instance of SQL on my desktop. I create an SQL Login named BITest
>> >> >> > and
>> >> >> > allow
>> >> >> > him into my Pubs DB. I then add him to the BulkAdmin fixed
>> >> >> > server
>> >> >> > role.
>> >> >> > When
>> >> >> > I have him try to Bulk Insert, I get:
>> >> >> >
>> >> >> > Server: Msg 8104, Level 16, State 2, Line 1
>> >> >> > The current user is not the database or object owner of table
>> >> >> > 'pubs.dbo.t_access'. Cannot perform SET operation.
>> >> >> >
>> >> >> > Which sort of indicates he needs to be in the db_owner role?
>> >> >> > Even
>> >> >> > though
>> >> >> > I
>> >> >> > think thats crap, I add him to db_owner, and then try to run my
>> >> >> > Bulk
>> >> >> > Insert
>> >> >> > again. This time I get:
>> >> >> >
>> >> >> > Server: Msg 4834, Level 16, State 1, Line 1
>> >> >> > You do not have permission to use the BULK INSERT statement.
>> >> >> >
>> >> >> > So, not only does it really appear that he nees to be part of
>> >> >> > db_owner,
>> >> >> > it
>> >> >> > still doesnt work. What gives?
>> >> >> >
>> >> >> > --
>> >> >> > TIA,
>> >> >> > ChrisR
>> >> >>
>> >> >>
>> >> >>
>> >>
>> >>
>> >>
>>

Bulk Insert fail for TempTable (bulkAdmi)

Hi,
I am trying to create a temp table and bulk insert data into that temp table
.
I am using the 'bulkinsert' login is a part of a server role bulkadmin and
has read access to databaseA.
Create table #My_Table
( Col1 varchar(14),
Col2 varchar(60))
then trying to bulk insert using
BULK INSERT #My_Table FROM '\\Network1\Data\TestDoc.txt' WITH
(Rowterminator='\n', FieldTerminator=',')
But it is giving me following error.
The current user is not the database or object owner of table '#My_Table ".
Cannot perform SET operation.
My 'bulkinsert' login has Access to DatabaseA, and also to tempdb.
Anyone have any idea why this is happening.. ? Your help is much appreciated
.
Thank youbluefish (bluefish@.discussions.microsoft.com) writes:
> I am trying to create a temp table and bulk insert data into that temp
> table.
> I am using the 'bulkinsert' login is a part of a server role bulkadmin
> and has read access to databaseA.
> Create table #My_Table
> ( Col1 varchar(14),
> Col2 varchar(60))
> then trying to bulk insert using
> BULK INSERT #My_Table FROM '\\Network1\Data\TestDoc.txt' WITH
> (Rowterminator='\n', FieldTerminator=',')
> But it is giving me following error.
> The current user is not the database or object owner of table
> '#My_Table ".
> Cannot perform SET operation.
> My 'bulkinsert' login has Access to DatabaseA, and also to tempdb.
> Anyone have any idea why this is happening.. ? Your help is much
> appreciated.
This is a flaw in SQL Server. Temp tables are "owned" by uid = 1 in
sysobjects, so the user needs dbo rights in tempdb (which I don't
recommend.) You will have to stick to a permanent table.
See also
5cc04c2cf" target="_blank">http://groups.google.com/group/comp...r />
5cc04c2cf
ab18661
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||Thank you very much!
"Erland Sommarskog" wrote:

> bluefish (bluefish@.discussions.microsoft.com) writes:
> This is a flaw in SQL Server. Temp tables are "owned" by uid = 1 in
> sysobjects, so the user needs dbo rights in tempdb (which I don't
> recommend.) You will have to stick to a permanent table.
> See also
> http://groups.google.com/group/comp...3&hl=sv#5cc04c2
cfab18661
>
> --
> Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
> Books Online for SQL Server 2005 at
> http://www.microsoft.com/technet/pr...oads/books.mspx
> Books Online for SQL Server 2000 at
> http://www.microsoft.com/sql/prodin...ions/books.mspx
>|||Also found out that ddl_admin permission to tempdb works as well.
Thank you
Sam
"Erland Sommarskog" wrote:

> bluefish (bluefish@.discussions.microsoft.com) writes:
> This is a flaw in SQL Server. Temp tables are "owned" by uid = 1 in
> sysobjects, so the user needs dbo rights in tempdb (which I don't
> recommend.) You will have to stick to a permanent table.
> See also
> http://groups.google.com/group/comp...3&hl=sv#5cc04c2
cfab18661
>
> --
> Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
> Books Online for SQL Server 2005 at
> http://www.microsoft.com/technet/pr...oads/books.mspx
> Books Online for SQL Server 2000 at
> http://www.microsoft.com/sql/prodin...ions/books.mspx
>|||bluefish (bluefish@.discussions.microsoft.com) writes:
> Also found out that ddl_admin permission to tempdb works as well.
OK, that slightly better than db_owner rights, but not much.
It appears that this issue has been addressed in SQL 2005.
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx

BUILTIN\Amdministrators & sa login

Hi All ,
can i delete the 2 logins above ? tried deleting sa but could not
i actually deleted the BUILTIN\Administrators when i tried to access the
Enterprise Managers i could not connect anymore , how can i rectify this ?
what's the inital password for sa ? i changed it to sa after deleteing the
BUILTIN\Administrators and when i tried to use SQL server login with id sa &
pwd sa i got error "Login failed for user 'Sa' Reason : Not associated with a
trusted sql server connection' how can i rectify this as well ?
appreciate the advice from anyone
tks & rdgs
maxzsim wrote:
> Hi All ,
>
> can i delete the 2 logins above ? tried deleting sa but could not
You can't delete the "sa" account. Deleting the Adminsitrators group is
not a great idea because you can no longer easily assign users (like the
DBA) to the group for admin access. The group is meaningless if no one
is assigned, so leaving it there without any users should be fine.

> i actually deleted the BUILTIN\Administrators when i tried to access
> the Enterprise Managers i could not connect anymore , how can i
> rectify this ?
You're probably using a login to the server in the SQL EM registration
page that used to be in the administrator group. Why you would delete
the administrators group without first verifying you had a valid admin
account with which to manage the server is a little strange.

> what's the inital password for sa ? i changed it to sa after
> deleteing the BUILTIN\Administrators and when i tried to use SQL
> server login with id sa & pwd sa i got error "Login failed for user
> 'Sa' Reason : Not associated with a trusted sql server connection'
> how can i rectify this as well ?
>
Maybe your server is not set up for mixed-mode security. If not, you can
change the setting, but doing so I believe requires admin access. If you
have another admin account, you can log in and change the "sa" password.
If you don't know your "sa" password and don't have any other admin
accounts, you may be forced to rebuild the master database and reattach
your databases. The 'sa" password is set up during the installation and
has no default value. You could try using an empty password and see if
that works.
David G.
|||Hi David ,
tks for your advice i will try out. Actually i was trying to prevent
someone from loggin using the sa login id
rdgs
"David Gugick" wrote:

> maxzsim wrote:
> You can't delete the "sa" account. Deleting the Adminsitrators group is
> not a great idea because you can no longer easily assign users (like the
> DBA) to the group for admin access. The group is meaningless if no one
> is assigned, so leaving it there without any users should be fine.
>
> You're probably using a login to the server in the SQL EM registration
> page that used to be in the administrator group. Why you would delete
> the administrators group without first verifying you had a valid admin
> account with which to manage the server is a little strange.
>
> Maybe your server is not set up for mixed-mode security. If not, you can
> change the setting, but doing so I believe requires admin access. If you
> have another admin account, you can log in and change the "sa" password.
> If you don't know your "sa" password and don't have any other admin
> accounts, you may be forced to rebuild the master database and reattach
> your databases. The 'sa" password is set up during the installation and
> has no default value. You could try using an empty password and see if
> that works.
>
> --
> David G.
>
|||maxzsim wrote:
> Hi David ,
> tks for your advice i will try out. Actually i was trying to prevent
> someone from loggin using the sa login id
>
The best way to do that is set SQL Server up to use Integrated Security
only. Without SQL Security, no one could log on using "sa" even if they
knew the password. But you need the "sa" account there and the best way
to secure it is to give it a nasty password. You do need at least one
administrator to manage the server. It's better to use integrated
security for this and add the domain user into the Administrators group.
That way, if the employeee should leave and the login removed from the
server, the backup is to enable mixed-mode security and log in using the
"sa" account.
David Gugick
Imceda Software
www.imceda.com

BUILTIN\Amdministrators & sa login

Hi All ,
can i delete the 2 logins above ? tried deleting sa but could not
i actually deleted the BUILTIN\Administrators when i tried to access the
Enterprise Managers i could not connect anymore , how can i rectify this ?
what's the inital password for sa ? i changed it to sa after deleteing the
BUILTIN\Administrators and when i tried to use SQL server login with id sa &
pwd sa i got error "Login failed for user 'Sa' Reason : Not associated with a
trusted sql server connection' how can i rectify this as well ?
appreciate the advice from anyone
tks & rdgsmaxzsim wrote:
> Hi All ,
>
> can i delete the 2 logins above ? tried deleting sa but could not
You can't delete the "sa" account. Deleting the Adminsitrators group is
not a great idea because you can no longer easily assign users (like the
DBA) to the group for admin access. The group is meaningless if no one
is assigned, so leaving it there without any users should be fine.
> i actually deleted the BUILTIN\Administrators when i tried to access
> the Enterprise Managers i could not connect anymore , how can i
> rectify this ?
You're probably using a login to the server in the SQL EM registration
page that used to be in the administrator group. Why you would delete
the administrators group without first verifying you had a valid admin
account with which to manage the server is a little strange.
> what's the inital password for sa ? i changed it to sa after
> deleteing the BUILTIN\Administrators and when i tried to use SQL
> server login with id sa & pwd sa i got error "Login failed for user
> 'Sa' Reason : Not associated with a trusted sql server connection'
> how can i rectify this as well ?
>
Maybe your server is not set up for mixed-mode security. If not, you can
change the setting, but doing so I believe requires admin access. If you
have another admin account, you can log in and change the "sa" password.
If you don't know your "sa" password and don't have any other admin
accounts, you may be forced to rebuild the master database and reattach
your databases. The 'sa" password is set up during the installation and
has no default value. You could try using an empty password and see if
that works.
David G.|||Hi David ,
tks for your advice i will try out. Actually i was trying to prevent
someone from loggin using the sa login id
rdgs
"David Gugick" wrote:
> maxzsim wrote:
> > Hi All ,
> >
> >
> > can i delete the 2 logins above ? tried deleting sa but could not
> You can't delete the "sa" account. Deleting the Adminsitrators group is
> not a great idea because you can no longer easily assign users (like the
> DBA) to the group for admin access. The group is meaningless if no one
> is assigned, so leaving it there without any users should be fine.
> >
> > i actually deleted the BUILTIN\Administrators when i tried to access
> > the Enterprise Managers i could not connect anymore , how can i
> > rectify this ?
> You're probably using a login to the server in the SQL EM registration
> page that used to be in the administrator group. Why you would delete
> the administrators group without first verifying you had a valid admin
> account with which to manage the server is a little strange.
> >
> > what's the inital password for sa ? i changed it to sa after
> > deleteing the BUILTIN\Administrators and when i tried to use SQL
> > server login with id sa & pwd sa i got error "Login failed for user
> > 'Sa' Reason : Not associated with a trusted sql server connection'
> > how can i rectify this as well ?
> >
> Maybe your server is not set up for mixed-mode security. If not, you can
> change the setting, but doing so I believe requires admin access. If you
> have another admin account, you can log in and change the "sa" password.
> If you don't know your "sa" password and don't have any other admin
> accounts, you may be forced to rebuild the master database and reattach
> your databases. The 'sa" password is set up during the installation and
> has no default value. You could try using an empty password and see if
> that works.
>
> --
> David G.
>|||maxzsim wrote:
> Hi David ,
> tks for your advice i will try out. Actually i was trying to prevent
> someone from loggin using the sa login id
>
The best way to do that is set SQL Server up to use Integrated Security
only. Without SQL Security, no one could log on using "sa" even if they
knew the password. But you need the "sa" account there and the best way
to secure it is to give it a nasty password. You do need at least one
administrator to manage the server. It's better to use integrated
security for this and add the domain user into the Administrators group.
That way, if the employeee should leave and the login removed from the
server, the backup is to enable mixed-mode security and log in using the
"sa" account.
--
David Gugick
Imceda Software
www.imceda.com

BUILTIN\Amdministrators & sa login

Hi All ,
can i delete the 2 logins above ? tried deleting sa but could not
i actually deleted the BUILTIN\Administrators when i tried to access the
Enterprise Managers i could not connect anymore , how can i rectify this ?
what's the inital password for sa ? i changed it to sa after deleteing the
BUILTIN\Administrators and when i tried to use SQL server login with id sa
&
pwd sa i got error "Login failed for user 'Sa' Reason : Not associated with
a
trusted sql server connection' how can i rectify this as well ?
appreciate the advice from anyone
tks & rdgsmaxzsim wrote:
> Hi All ,
>
> can i delete the 2 logins above ? tried deleting sa but could not
You can't delete the "sa" account. Deleting the Adminsitrators group is
not a great idea because you can no longer easily assign users (like the
DBA) to the group for admin access. The group is meaningless if no one
is assigned, so leaving it there without any users should be fine.

> i actually deleted the BUILTIN\Administrators when i tried to access
> the Enterprise Managers i could not connect anymore , how can i
> rectify this ?
You're probably using a login to the server in the SQL EM registration
page that used to be in the administrator group. Why you would delete
the administrators group without first verifying you had a valid admin
account with which to manage the server is a little strange.

> what's the inital password for sa ? i changed it to sa after
> deleteing the BUILTIN\Administrators and when i tried to use SQL
> server login with id sa & pwd sa i got error "Login failed for user
> 'Sa' Reason : Not associated with a trusted sql server connection'
> how can i rectify this as well ?
>
Maybe your server is not set up for mixed-mode security. If not, you can
change the setting, but doing so I believe requires admin access. If you
have another admin account, you can log in and change the "sa" password.
If you don't know your "sa" password and don't have any other admin
accounts, you may be forced to rebuild the master database and reattach
your databases. The 'sa" password is set up during the installation and
has no default value. You could try using an empty password and see if
that works.
David G.|||Hi David ,
tks for your advice i will try out. Actually i was trying to prevent
someone from loggin using the sa login id
rdgs
"David Gugick" wrote:

> maxzsim wrote:
> You can't delete the "sa" account. Deleting the Adminsitrators group is
> not a great idea because you can no longer easily assign users (like the
> DBA) to the group for admin access. The group is meaningless if no one
> is assigned, so leaving it there without any users should be fine.
>
> You're probably using a login to the server in the SQL EM registration
> page that used to be in the administrator group. Why you would delete
> the administrators group without first verifying you had a valid admin
> account with which to manage the server is a little strange.
>
> Maybe your server is not set up for mixed-mode security. If not, you can
> change the setting, but doing so I believe requires admin access. If you
> have another admin account, you can log in and change the "sa" password.
> If you don't know your "sa" password and don't have any other admin
> accounts, you may be forced to rebuild the master database and reattach
> your databases. The 'sa" password is set up during the installation and
> has no default value. You could try using an empty password and see if
> that works.
>
> --
> David G.
>|||maxzsim wrote:
> Hi David ,
> tks for your advice i will try out. Actually i was trying to prevent
> someone from loggin using the sa login id
>
The best way to do that is set SQL Server up to use Integrated Security
only. Without SQL Security, no one could log on using "sa" even if they
knew the password. But you need the "sa" account there and the best way
to secure it is to give it a nasty password. You do need at least one
administrator to manage the server. It's better to use integrated
security for this and add the domain user into the Administrators group.
That way, if the employeee should leave and the login removed from the
server, the backup is to enable mixed-mode security and log in using the
"sa" account.
David Gugick
Imceda Software
www.imceda.com

builtin\administrators login and database access

How do I remove db_owner access from the
builtin\administrators sql login?
The db_owner and sysadmin roles have been assigned to the
windows domain account that starts SQL Server and the sa
login for all db's.
I need to remove this for secutiry/legal reason.
Any problems if I just remove the builtin\administrators
login?
Thanks."Matt Troska" <matt.troska@.co.mcleod.mn.us> wrote in message
news:495f01c3e42f$efd44e50$a501280a@.phx.gbl...

quote:

---

> How do I remove db_owner access from the
> builtin\administrators sql login?

---

You don't want to do that...

quote:

---

> The db_owner and sysadmin roles have been assigned to the
> windows domain account that starts SQL Server and the sa
> login for all db's.
> I need to remove this for secutiry/legal reason.
> Any problems if I just remove the builtin\administrators
> login?

---

That's the correct approach, as long as you've granted another group/user
sysadmin equivalence, then you can safely delete the builtin\administrators
group.
After I install SQL Server and setup the security, deleting the
builtin\administrators group is usually one of the first steps I take.
Steve

BUILTIN\Administrators Login

I would like to remove the BUILTIN\Administrators Login
from SQL Server 2000 for security purposes.
Will there be any problems with SQL Server 2000 running
properly if I do this?
Thank you.Whether you get problems or not depends. The following
article has an more information section with links to some
issues that could come up:
INF: How to impede Windows NT administrators from
administering a clustered instance of SQL Server
http://support.microsoft.com/?id=263712
-Sue
On Mon, 22 Mar 2004 12:58:47 -0800, "Mike"
<anonymous@.discussions.microsoft.com> wrote:

>I would like to remove the BUILTIN\Administrators Login
>from SQL Server 2000 for security purposes.
>Will there be any problems with SQL Server 2000 running
>properly if I do this?
>Thank you.|||Hi,
I had problems in the below when I removed "Syadmin role" from
BuildIN/Administrators. So I have given back the sysadmin role to solve the
issue.
1. FULL Text Indexing
2. Maintenance Plans
So do a test in test server for couple of weeks and then implement in
Production server.
Known issues after removal ,
Some things to be aware of:
Q237604 PRB: SQL Server Agent Does Not Start and Displays Error 18456
Q295034 FIX: MSSearch Takes 100% CPU if BUILTIN\Administrators Removed
Q317746 PRB: SQL Server Full-Text Search Does Not Populate Catalogs
Thanks
Hari
MCDBA
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:d9mu5054kffi4f8olts36mpa8du6um98q9@.
4ax.com...
> Whether you get problems or not depends. The following
> article has an more information section with links to some
> issues that could come up:
> INF: How to impede Windows NT administrators from
> administering a clustered instance of SQL Server
> http://support.microsoft.com/?id=263712
> -Sue
> On Mon, 22 Mar 2004 12:58:47 -0800, "Mike"
> <anonymous@.discussions.microsoft.com> wrote:
>
>

Builtin\Administrator login

Hi All,
I have few questions about above mentioned login.
1. What is this login for?
2. Can I delete it without causing any problems? I don't want the network guys have the sysadmin role to the SQL Server.
Can you tell me what I need to do? Thanks.This is the login that is used by administrators on the local machine. It is handy in case you forget the sa password, and need to change it. In order to disable it, set up a DBA group, and add it to the sysadmin server role before doing anything else. Then you can safely drop the builtin administrators group. If you drop your DBA group from the domain after that, then all of your SQL Servers are auto-magically transmogrified into glorified server room space heaters.|||If you drop your DBA group from the domain after that, then all of your SQL Servers are auto-magically transmogrified into glorified server room space heaters.

LOL:D

Do you speak from experience? Or is this...ahem...second-hand knowledge?

Regards,

hmscott

Builtin\Administrator login

Hi All,
How can I tell what account SQL Agent configured to start up with? Local or domain?In Enterprise Mangler, right click on the SQL Server Agent and select Properties. If you can't connect to the server, look at the Service in Windows services, and click the "Log On" tab to see the login information.

-PatP|||I looked in Enterprise Manager and the radio button next to System Account is selected. Is it local or domain?|||Local. If it were a domain administrator, the domain name would be a prefix such as MyDomain\Administrator in the box.

-PatP|||Thank you.

Building a community

Hi!

Hello. I have now started to build my own community. And I have some questions on the database.

For the users to login I use the login control and all the users information is stored in the ASPNETDB.MDF database.
In the web.config file I have created some profiles for saving some information about the users (Name, Birth, Town) and so on.

Now. All the users in this community will have their own profile page, Guestbooks ++.

So I was wondering if I should create tables for all features like guestbook, profile pages or should I do this by using Profile (ASP.NET).

How many users does ASPNETDB support?.

I suppose it depends on which server are you running it, Mostly it is limited to database size and is limited to

4 GB maximum database size on SQL Express but no limit in paid versions.

And it probably depends on your system speed to prevent user to wait couple of minutes to login.

And you can always create separate user database for each of your web page if 4GB is too small for you.

Thanks

BUILDIN\Administrator's login account

I am going to remove the BUILDIN\Administrator's log account as recommneded
for the security reason , is there anyone has thouhgts on how good and (or)
how bad it can be if I remove it ? and what if I need this acccount later?
can I put it back?
Thanks a lotI think it'll be better to rename it in Local Policy Editor rather than
remove it.
"Catelin Wang" <CatelinWang@.discussions.microsoft.com> glsD:A3C2C86C-21BC-4A62-AE6
7-B8AE0B6ADAD8@.microsoft.com...
>I am going to remove the BUILDIN\Administrator's log account as recommneded
> for the security reason , is there anyone has thouhgts on how good and
> (or)
> how bad it can be if I remove it ? and what if I need this acccount later?
> can I put it back?
> Thanks a lot
>|||You can remove the builtin\administrators group from SQL
Server. However, under some scenarios, this can cause
problems. Whether you experience problems or not depends.
The following article has a more information section with
links to some issues that could come up:
INF: How to impede Windows NT administrators from
administering a clustered instance of SQL Server
http://support.microsoft.com/?id=263712
You can add the account back later by executing the
following in Query Analyzer:
EXEC sp_grantlogin 'BUILTIN\Administrators'
By default, the group is a member of the sysadmins sql
server role. If you wanted this back as well, you could
execute the following:
EXEC sp_addsrvrolemember 'BUILTIN\Administrators' ,
'sysadmin'
-Sue
On Thu, 28 Jul 2005 18:38:55 -0700, Catelin Wang
<CatelinWang@.discussions.microsoft.com> wrote:

>I am going to remove the BUILDIN\Administrator's log account as recommneded
>for the security reason , is there anyone has thouhgts on how good and (or)
>how bad it can be if I remove it ? and what if I need this acccount later?
>can I put it back?
>Thanks a lot|||Thanks a lot.
What if I uncheck the 'system administror' role in SQL Srver login, does ths
work the same?
"Catelin Wang" wrote:

> I am going to remove the BUILDIN\Administrator's log account as recommnede
d
> for the security reason , is there anyone has thouhgts on how good and (or
)
> how bad it can be if I remove it ? and what if I need this acccount later?
> can I put it back?
> Thanks a lot
>|||Technically it's not the same as removing the account. When
you remove the group from the sysadmin server role, they can
still log into SQL Server but aren't sysadmins. If they
aren't added to any databases, server or database roles,
they would have whatever access the guest account has. Which
way to go depends on what you want to accomplish.
-Sue
On Fri, 29 Jul 2005 06:45:02 -0700, Catelin Wang
<CatelinWang@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Thanks a lot.
>What if I uncheck the 'system administror' role in SQL Srver login, does th
s
>work the same?
>
>"Catelin Wang" wrote:
>|||Thanks Sue, your messages are very helpful.
"Sue Hoegemeier" wrote:

> Technically it's not the same as removing the account. When
> you remove the group from the sysadmin server role, they can
> still log into SQL Server but aren't sysadmins. If they
> aren't added to any databases, server or database roles,
> they would have whatever access the guest account has. Which
> way to go depends on what you want to accomplish.
> -Sue
> On Fri, 29 Jul 2005 06:45:02 -0700, Catelin Wang
> <CatelinWang@.discussions.microsoft.com> wrote:
>
>

BUILDIN\Administrator's login account

I am going to remove the BUILDIN\Administrator's log account as recommneded
for the security reason , is there anyone has thouhgts on how good and (or)
how bad it can be if I remove it ? and what if I need this acccount later?
can I put it back?
Thanks a lotI think it'll be better to rename it in Local Policy Editor rather than
remove it.
"Catelin Wang" <CatelinWang@.discussions.microsoft.com> ¼¶¼g©ó¶l¥ó·s»D:A3C2C86C-21BC-4A62-AE67-B8AE0B6ADAD8@.microsoft.com...
>I am going to remove the BUILDIN\Administrator's log account as recommneded
> for the security reason , is there anyone has thouhgts on how good and
> (or)
> how bad it can be if I remove it ? and what if I need this acccount later?
> can I put it back?
> Thanks a lot
>|||You can remove the builtin\administrators group from SQL
Server. However, under some scenarios, this can cause
problems. Whether you experience problems or not depends.
The following article has a more information section with
links to some issues that could come up:
INF: How to impede Windows NT administrators from
administering a clustered instance of SQL Server
http://support.microsoft.com/?id=263712
You can add the account back later by executing the
following in Query Analyzer:
EXEC sp_grantlogin 'BUILTIN\Administrators'
By default, the group is a member of the sysadmins sql
server role. If you wanted this back as well, you could
execute the following:
EXEC sp_addsrvrolemember 'BUILTIN\Administrators' ,
'sysadmin'
-Sue
On Thu, 28 Jul 2005 18:38:55 -0700, Catelin Wang
<CatelinWang@.discussions.microsoft.com> wrote:
>I am going to remove the BUILDIN\Administrator's log account as recommneded
>for the security reason , is there anyone has thouhgts on how good and (or)
>how bad it can be if I remove it ? and what if I need this acccount later?
>can I put it back?
>Thanks a lot|||Thanks a lot.
What if I uncheck the 'system administror' role in SQL Srver login, does ths
work the same?
"Catelin Wang" wrote:
> I am going to remove the BUILDIN\Administrator's log account as recommneded
> for the security reason , is there anyone has thouhgts on how good and (or)
> how bad it can be if I remove it ? and what if I need this acccount later?
> can I put it back?
> Thanks a lot
>|||Technically it's not the same as removing the account. When
you remove the group from the sysadmin server role, they can
still log into SQL Server but aren't sysadmins. If they
aren't added to any databases, server or database roles,
they would have whatever access the guest account has. Which
way to go depends on what you want to accomplish.
-Sue
On Fri, 29 Jul 2005 06:45:02 -0700, Catelin Wang
<CatelinWang@.discussions.microsoft.com> wrote:
>Thanks a lot.
>What if I uncheck the 'system administror' role in SQL Srver login, does ths
>work the same?
>
>"Catelin Wang" wrote:
>> I am going to remove the BUILDIN\Administrator's log account as recommneded
>> for the security reason , is there anyone has thouhgts on how good and (or)
>> how bad it can be if I remove it ? and what if I need this acccount later?
>> can I put it back?
>> Thanks a lot|||Thanks Sue, your messages are very helpful.
"Sue Hoegemeier" wrote:
> Technically it's not the same as removing the account. When
> you remove the group from the sysadmin server role, they can
> still log into SQL Server but aren't sysadmins. If they
> aren't added to any databases, server or database roles,
> they would have whatever access the guest account has. Which
> way to go depends on what you want to accomplish.
> -Sue
> On Fri, 29 Jul 2005 06:45:02 -0700, Catelin Wang
> <CatelinWang@.discussions.microsoft.com> wrote:
> >Thanks a lot.
> >
> >What if I uncheck the 'system administror' role in SQL Srver login, does ths
> >work the same?
> >
> >
> >"Catelin Wang" wrote:
> >
> >> I am going to remove the BUILDIN\Administrator's log account as recommneded
> >> for the security reason , is there anyone has thouhgts on how good and (or)
> >> how bad it can be if I remove it ? and what if I need this acccount later?
> >> can I put it back?
> >>
> >> Thanks a lot
> >>
>

BUILDIN\Administrator's login account

I am going to remove the BUILDIN\Administrator's log account as recommneded
for the security reason , is there anyone has thouhgts on how good and (or)
how bad it can be if I remove it ? and what if I need this acccount later?
can I put it back?
Thanks a lot
I think it'll be better to rename it in Local Policy Editor rather than
remove it.
"Catelin Wang" <CatelinWang@.discussions.microsoft.com> glsD:A3C2C86C-21BC-4A62-AE67-B8AE0B6ADAD8@.microsoft.com...
>I am going to remove the BUILDIN\Administrator's log account as recommneded
> for the security reason , is there anyone has thouhgts on how good and
> (or)
> how bad it can be if I remove it ? and what if I need this acccount later?
> can I put it back?
> Thanks a lot
>
|||You can remove the builtin\administrators group from SQL
Server. However, under some scenarios, this can cause
problems. Whether you experience problems or not depends.
The following article has a more information section with
links to some issues that could come up:
INF: How to impede Windows NT administrators from
administering a clustered instance of SQL Server
http://support.microsoft.com/?id=263712
You can add the account back later by executing the
following in Query Analyzer:
EXEC sp_grantlogin 'BUILTIN\Administrators'
By default, the group is a member of the sysadmins sql
server role. If you wanted this back as well, you could
execute the following:
EXEC sp_addsrvrolemember 'BUILTIN\Administrators' ,
'sysadmin'
-Sue
On Thu, 28 Jul 2005 18:38:55 -0700, Catelin Wang
<CatelinWang@.discussions.microsoft.com> wrote:

>I am going to remove the BUILDIN\Administrator's log account as recommneded
>for the security reason , is there anyone has thouhgts on how good and (or)
>how bad it can be if I remove it ? and what if I need this acccount later?
>can I put it back?
>Thanks a lot
|||Thanks a lot.
What if I uncheck the 'system administror' role in SQL Srver login, does ths
work the same?
"Catelin Wang" wrote:

> I am going to remove the BUILDIN\Administrator's log account as recommneded
> for the security reason , is there anyone has thouhgts on how good and (or)
> how bad it can be if I remove it ? and what if I need this acccount later?
> can I put it back?
> Thanks a lot
>
|||Technically it's not the same as removing the account. When
you remove the group from the sysadmin server role, they can
still log into SQL Server but aren't sysadmins. If they
aren't added to any databases, server or database roles,
they would have whatever access the guest account has. Which
way to go depends on what you want to accomplish.
-Sue
On Fri, 29 Jul 2005 06:45:02 -0700, Catelin Wang
<CatelinWang@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Thanks a lot.
>What if I uncheck the 'system administror' role in SQL Srver login, does ths
>work the same?
>
>"Catelin Wang" wrote:
|||Thanks Sue, your messages are very helpful.
"Sue Hoegemeier" wrote:

> Technically it's not the same as removing the account. When
> you remove the group from the sysadmin server role, they can
> still log into SQL Server but aren't sysadmins. If they
> aren't added to any databases, server or database roles,
> they would have whatever access the guest account has. Which
> way to go depends on what you want to accomplish.
> -Sue
> On Fri, 29 Jul 2005 06:45:02 -0700, Catelin Wang
> <CatelinWang@.discussions.microsoft.com> wrote:
>
>