myLittleTools Community Forum

Welcome Guest Search | Active Topics | Members | Log In | Register

Planning to buy, but... Options · View
WimVM
Posted: Wednesday, May 02, 2007 11:11:54 AM
Rank: Newbie
Groups: Member

Joined: 5/2/2007
Posts: 1
Points: 0
Location: BE
Hello,

Our company is planning to buy myLittleAdmin for SQL 2005 to use it in our hosting platform for offering SQL 2005 hosting.

One of our main questions is more related to SQL. How do we set-up the SQL 2005 server AND SECURITY to be able to work with myLittleAdmin?

But most of all to make sure our customers only can access there own database and can not cause any harm to other client databases.

Is there some guide available that goes in to more detail about securing the SQL server for use with your product? Or can you provide us a list of actions to take to secure our SQL server.

I do not ask for a 100% guaranteed document, ofcourse this doesn't exist. But I miss some basic information on this topic on your website. Like, will your tool set some standard security on the created databases in the tool to isolate them for other customers. Or is everything up to the user/dbowner?

Thanks.
elian
Posted: Wednesday, May 02, 2007 1:09:18 PM

Rank: Administration
Groups: Administration

Joined: 9/11/2006
Posts: 605
Points: 649
Location: Enghien Les Bains, France
Wim
Thanks a lot for contacting us.

Quote:
How do we set-up the SQL 2005 server AND SECURITY to be able to work with myLittleAdmin?

There is no specific configuration to make MLA work with MSSQL2005. You just need to install MLA on your IIS server.

Quote:
But most of all to make sure our customers only can access there own database and can not cause any harm to other client databases.

This is the normal behavior of MLA. Users can only see the database they have an account for.

Quote:
Or can you provide us a list of actions to take to secure our SQL server.

Just configure your MSSQL2005 the same way you will configure it if you should not use MLA.

Quote:
Like, will your tool set some standard security on the created databases in the tool to isolate them for other customers. Or is everything up to the user/dbowner?

Once again, this is the normal behavior. Anyway, a lot of webhosters prefer to restrict their customers to db_datareader, db_datawriter, db_ddladmin roles.

Let us know if we can be of further assistance
Users browsing this topic
Guest


You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.

Main Forum RSS : RSS

Theme created by myLittleTools
Powered by Yet Another Forum.net version 1.9.1.8 (NET v2.0) - 3/29/2008
Copyright © 2003-2008 Yet Another Forum.net. All rights reserved.