Question about schema?
-
I am working on a legacy app with a SqlServer DB I am about to create 18 brand new table to support new functionality I'm going to add Just for clarity sake I was thinking to create this table in a new schema (a bit like grouping my C# class by namespace / folder in my mind) But as I'm reading about schema I read that it has security associated with it.. :~ I don't want to make thing more complicated.. :(( (quite the opposite) So.. what's your take on shema? is it here for grouping things together for 1. clarity / purpose 2. security
My programming get away... The Blog... DirectX for WinRT/C# since 2013! Taking over the world since 1371!
-
I am working on a legacy app with a SqlServer DB I am about to create 18 brand new table to support new functionality I'm going to add Just for clarity sake I was thinking to create this table in a new schema (a bit like grouping my C# class by namespace / folder in my mind) But as I'm reading about schema I read that it has security associated with it.. :~ I don't want to make thing more complicated.. :(( (quite the opposite) So.. what's your take on shema? is it here for grouping things together for 1. clarity / purpose 2. security
My programming get away... The Blog... DirectX for WinRT/C# since 2013! Taking over the world since 1371!
This is a flavour of the month thing, some do some don't. Security allows you to assign specific users to a schema, really useful if your users have query access to the database but if you use a schema just for you to identify the functionality grouping simply give all users the rights to the schema. Another issue will be your DAL, it will need to support multiple schemas, this one bit me many years ago as I assumed dbo only.
Never underestimate the power of human stupidity RAH
-
I am working on a legacy app with a SqlServer DB I am about to create 18 brand new table to support new functionality I'm going to add Just for clarity sake I was thinking to create this table in a new schema (a bit like grouping my C# class by namespace / folder in my mind) But as I'm reading about schema I read that it has security associated with it.. :~ I don't want to make thing more complicated.. :(( (quite the opposite) So.. what's your take on shema? is it here for grouping things together for 1. clarity / purpose 2. security
My programming get away... The Blog... DirectX for WinRT/C# since 2013! Taking over the world since 1371!
The purpose of the schema is security, how you use it is up to you. It's not an overly big deal to give the user associated with one schema rights on another schema.
Be excellent to each other. And... PARTY ON, DUDES! Abraham Lincoln
-
I am working on a legacy app with a SqlServer DB I am about to create 18 brand new table to support new functionality I'm going to add Just for clarity sake I was thinking to create this table in a new schema (a bit like grouping my C# class by namespace / folder in my mind) But as I'm reading about schema I read that it has security associated with it.. :~ I don't want to make thing more complicated.. :(( (quite the opposite) So.. what's your take on shema? is it here for grouping things together for 1. clarity / purpose 2. security
My programming get away... The Blog... DirectX for WinRT/C# since 2013! Taking over the world since 1371!
After you CREATE SCHEMA you'll notice that the object, if I could call it that for a moment, is found in the Security folder of the Object Browser tree. But as far as using SCHEMA as one would an "idea" in the "scheme of things" ... it's nature is perfect for that. I use it to isolate dev stages as I work on scripts. Testing procedures, isolating a vast array of data tables by filtering them via SCHEMA, in Object Viewer, is very easy. In fact one of the only downsides to using SQL Server Management Studio happens to be that only one SCHEMA at a time is filterable. That and a very aggrevating lack of code editor collapsablilty (-/+) as in VS. But that's rant for another holiday. ARRRRGHHHH me buckoe.
-
I am working on a legacy app with a SqlServer DB I am about to create 18 brand new table to support new functionality I'm going to add Just for clarity sake I was thinking to create this table in a new schema (a bit like grouping my C# class by namespace / folder in my mind) But as I'm reading about schema I read that it has security associated with it.. :~ I don't want to make thing more complicated.. :(( (quite the opposite) So.. what's your take on shema? is it here for grouping things together for 1. clarity / purpose 2. security
My programming get away... The Blog... DirectX for WinRT/C# since 2013! Taking over the world since 1371!