Remove BUILTIN\Administrators from SQL 2005

We have a server shared by two project teams. To tight the security, I want to remove BUILTIN\Administrators off the public and sysadmin server roles. My question: any thing I should pay special attention ? I use LocalSystem to start all SQL Service. I know this is not a very good pratice yet I have no choice as our company network is a mixed of windows and novell, we do not have AD.

Make sure that you have a sysadmin left after removing builtin\administrators. I have seen sql servers in integrated mode where someone removed builtin\administrators and then nobody could administer the server.

Local System is very powerful. Any code executed by SQL Server can change anything on the windows box so if you are running untrusted code inside SQL Server you need to be aware of that fact and the potential threat it represents.

to remove builtin\administraotrs

exec sp_dropsrvrolemember [BUILTIN\Administrators] , sysadmin

go

drop login [BUILTIN\Administrators]

go

hth,

-Steven Gott

S/DET

SQL Server

|||

Hi,

What about NT AUTHORITY\System account?

Is it needed?

Regards,

Jeremy

|||

Some management tools may be using it (for example MOM).

-Raul Garcia

SDE/T

SQL Server Engine

Remove BUILTIN\Administrators from SQL 2005

We have a server shared by two project teams. To tight the security, I want to remove BUILTIN\Administrators off the public and sysadmin server roles. My question: any thing I should pay special attention ? I use LocalSystem to start all SQL Service. I know this is not a very good pratice yet I have no choice as our company network is a mixed of windows and novell, we do not have AD.

Make sure that you have a sysadmin left after removing builtin\administrators. I have seen sql servers in integrated mode where someone removed builtin\administrators and then nobody could administer the server.

Local System is very powerful. Any code executed by SQL Server can change anything on the windows box so if you are running untrusted code inside SQL Server you need to be aware of that fact and the potential threat it represents.

to remove builtin\administraotrs

exec sp_dropsrvrolemember [BUILTIN\Administrators] , sysadmin

go

drop login [BUILTIN\Administrators]

go

hth,

-Steven Gott

S/DET

SQL Server

|||

Hi,

What about NT AUTHORITY\System account?

Is it needed?

Regards,

Jeremy

|||

Some management tools may be using it (for example MOM).

-Raul Garcia

SDE/T

SQL Server Engine

Remote Sync -- SQL 2000

I am just beginning development of a new app and I need a little advice on
the best way to go about doing something.

The app is a project management tool for a construction company. Users in
the field will need to do remote updates both receiving and submitting data
back to the main office. I can't just make it a live web app because the
users will have to be able to work off line and sync data later (presumably
with a VPN connection).

What is the best way to go about this? I planned on using MSDE 2000 w/Access
front end. I will install MSDE on each laptop but what is the safest/most
reliable way to sync only that information which pertains to a specific user
along with other general information.

Any books that helpful with this specific issue? Any one have reusable
modules/code they'd be willing to send me?

TIA,

--JakeCXonsider replication, transactional or merge. Transactional is the
easier of the tow options but does mean that oly one side can make
changes to the data. With merge both sides cna change the data and you
create a set of rules to decide whic update is accepted.

Jake Jessup wrote:

> I am just beginning development of a new app and I need a little advice on
> the best way to go about doing something.
> The app is a project management tool for a construction company. Users in
> the field will need to do remote updates both receiving and submitting data
> back to the main office. I can't just make it a live web app because the
> users will have to be able to work off line and sync data later (presumably
> with a VPN connection).
> What is the best way to go about this? I planned on using MSDE 2000 w/Access
> front end. I will install MSDE on each laptop but what is the safest/most
> reliable way to sync only that information which pertains to a specific user
> along with other general information.
> Any books that helpful with this specific issue? Any one have reusable
> modules/code they'd be willing to send me?
> TIA,
> --Jake
>

Remote Deployment

What's the easiest way to deploy a project to a remote server? Keep in mind there won't be any machine level access to the server housing the sql server.

Your question is bit short.
If you are talking about deployment of Analysis Services project you have several ways.

1. Change your BI Dev project properties to tell it to deploy to remote machine.

2. Use Deployment utility.

3. deploy your project first to the local Analysis Server and then use Synchronization or Backup/Restore to move data and metadata to a remote server.

I am sure you can be quite creative and find other ways to deploy your solution.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

Remote Connections error

While trying to transfer my website project to another computer I am encountering an error when tryng to run the solution. It gives me a "Does not allow remote connections". Why is this when on the original computer everything worked fine.

Walter

Does the error has anything to do with SQL server?

This error is common when there is a connection problem to SQL server.

Verify your connection string.Make sure SQL server is running. Make sure you are able to connect to the database.

Regards,

David

|||

I think I had an error similar to this before and therefore I'll assume that your problem is like mine and is associated with SQL Server. (I thinkneutrino is of the same persuasion.)

Now if I understand you correctly, you're trying to run a project on one pc and connect to a database on another pc. Therefore I think the problem is that SQL Server is rejecting your remote connection because it's not configured to accept it! You need to allow remote connections to that server.

See this article (How to configure SQL Server 2005 to allow remote connections ).

Now.. if you're problem isn't related to SQL Server ... well.. Ignore all of the above.