[dba-SQLServer] Schemas for separation of clients?

Gustav Brock gustav at cactus.dk
Thu Apr 2 12:00:43 CDT 2015


Thanks Francisco, that seems to be exactly what I was wondering about.

/gustav

________________________________________
Fra: dba-SQLServer <dba-sqlserver-bounces at databaseadvisors.com> på vegne af fhtapia at gmail.com <fhtapia at gmail.com>
Sendt: 2. april 2015 18:29
Til: Discussion concerning MS SQL Server
Emne: Re: [dba-SQLServer] Schemas for separation of clients?

Are you referring to the dataset just for a schema?

one method would be to do it via using MSSMS and scripting out both the
schema and data:
http://stackoverflow.com/questions/2254878/is-there-a-way-to-export-an-entire-sql-server-database-schema-and-data-to-te

On Tue, Mar 31, 2015 at 10:23 AM Gustav Brock <gustav at cactus.dk> wrote:

> Thanks Francisco, I'll mark that.
>
> Next question is if you can manage backup and restore of individual
> schemas - if perhaps not easily then, at least, reliably?
>
> /gustav
>
> -----Oprindelig meddelelse-----
> Fra: dba-SQLServer [mailto:dba-sqlserver-bounces at databaseadvisors.com] På
> vegne af fhtapia at gmail.com
> Sendt: 31. marts 2015 15:42
> Til: Discussion concerning MS SQL Server
> Emne: Re: [dba-SQLServer] Schemas for separation of clients?
>
> Hello Mark,
>   If the intent is to provide a segregated security space for multiple
> users, then Schema's offers a huge advantage.  They are simply containers
> to an entire database set per grouping.
>
> It is much simpler to set security based on the schema, than to focus on
> the individual db Table.  not to mention, the peril of accidentally
> returning data back to a customer that is not their own because the
> query/sproc had access to any data in the table.
>
> more solid points:
>
> http://blog.sqlauthority.com/2009/09/07/sql-server-importance-of-database-
> schemas-in-sql-server/
>
> --
> Francisco


More information about the dba-SQLServer mailing list