Storing related tables and toolboxes within feature dataset? The 2019 Stack Overflow Developer...
How can I create a character who can assume the widest possible range of creature sizes?
If Wish Duplicates Simulacrum, Are Existing Duplicates Destroyed?
Inversion Puzzle
Does it makes sense to buy a new cycle to learn riding?
Why is the maximum length of openwrt’s root password 8 characters?
Why can Shazam do this?
Output the Arecibo Message
"To split hairs" vs "To be pedantic"
How to create dashed lines/arrows in Illustrator
Why Did Howard Stark Use All The Vibranium They Had On A Prototype Shield?
Lethal sonic weapons
Falsification in Math vs Science
Springs with some finite mass
Where does the "burst of radiance" from Holy Weapon originate?
Evaluating number of iteration with a certain map with While
Is three citations per paragraph excessive for undergraduate research paper?
Is it possible for the two major parties in the UK to form a coalition with each other instead of a much smaller party?
Dual Citizen. Exited the US on Italian passport recently
In microwave frequencies, do you use a circulator when you need a (near) perfect diode?
What is this 4-propeller plane?
How to answer pointed "are you quitting" questioning when I don't want them to suspect
How was Skylab's orbit inclination chosen?
What do the Banks children have against barley water?
Is the gradient of the self-intersections of a curve zero?
Storing related tables and toolboxes within feature dataset?
The 2019 Stack Overflow Developer Survey Results Are InIs it possible to re-point operational layers ArcGIS Mobile projects v.3.0ArcSDE/ST_Geometry: Can I store polygon and point geometries in same row?Understanding ArcGIS Server connection typesIs it possible to force uppercase in a geodatabase string field?File GeoDatabase Table is too large to export?enable enterprise geodatabase errorWorking on databased-stored-geodatabase with a ArcGIS for Desktop standard license?Retrieving deleted records from feature dataset in enterprise geodatabase?Working with a small spatial extent from a large dataset in ArcMapPortal And ArcSDE Geodatabase: Feature Datasets or Not
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
I am new to Enterprise geodatabases and am looking for some information regarding data structure and storage. Within my organization, we would like to store individual projects by feature dataset within a single Enterprise geodatabase. To my knowledge this is possible if the data does not contain any related tables or associated toolboxes.
Is it possible to store related tables and toolboxes within a feature dataset?
My goal is to not create an Enterprise geodatabase for each individual project.
arcgis-server enterprise-geodatabase sql-server feature-dataset
add a comment |
I am new to Enterprise geodatabases and am looking for some information regarding data structure and storage. Within my organization, we would like to store individual projects by feature dataset within a single Enterprise geodatabase. To my knowledge this is possible if the data does not contain any related tables or associated toolboxes.
Is it possible to store related tables and toolboxes within a feature dataset?
My goal is to not create an Enterprise geodatabase for each individual project.
arcgis-server enterprise-geodatabase sql-server feature-dataset
Geodatabase Diagrammer for 10X > arcgis.com/home/item.html?id=a378b48be11b45b5bb25254643304cb7
– Mapperz♦
8 hours ago
1
Best practice is to only place the feature classes which are absolutely required to be in feature datasets together. It's an antipattern to use feature datasets as a folder to glom related data together; doing this slows the actual FDS operations with additional checking and locking.
– Vince
7 hours ago
add a comment |
I am new to Enterprise geodatabases and am looking for some information regarding data structure and storage. Within my organization, we would like to store individual projects by feature dataset within a single Enterprise geodatabase. To my knowledge this is possible if the data does not contain any related tables or associated toolboxes.
Is it possible to store related tables and toolboxes within a feature dataset?
My goal is to not create an Enterprise geodatabase for each individual project.
arcgis-server enterprise-geodatabase sql-server feature-dataset
I am new to Enterprise geodatabases and am looking for some information regarding data structure and storage. Within my organization, we would like to store individual projects by feature dataset within a single Enterprise geodatabase. To my knowledge this is possible if the data does not contain any related tables or associated toolboxes.
Is it possible to store related tables and toolboxes within a feature dataset?
My goal is to not create an Enterprise geodatabase for each individual project.
arcgis-server enterprise-geodatabase sql-server feature-dataset
arcgis-server enterprise-geodatabase sql-server feature-dataset
edited 1 min ago
PolyGeo♦
53.9k1781246
53.9k1781246
asked 8 hours ago
DaykrayDaykray
916
916
Geodatabase Diagrammer for 10X > arcgis.com/home/item.html?id=a378b48be11b45b5bb25254643304cb7
– Mapperz♦
8 hours ago
1
Best practice is to only place the feature classes which are absolutely required to be in feature datasets together. It's an antipattern to use feature datasets as a folder to glom related data together; doing this slows the actual FDS operations with additional checking and locking.
– Vince
7 hours ago
add a comment |
Geodatabase Diagrammer for 10X > arcgis.com/home/item.html?id=a378b48be11b45b5bb25254643304cb7
– Mapperz♦
8 hours ago
1
Best practice is to only place the feature classes which are absolutely required to be in feature datasets together. It's an antipattern to use feature datasets as a folder to glom related data together; doing this slows the actual FDS operations with additional checking and locking.
– Vince
7 hours ago
Geodatabase Diagrammer for 10X > arcgis.com/home/item.html?id=a378b48be11b45b5bb25254643304cb7
– Mapperz♦
8 hours ago
Geodatabase Diagrammer for 10X > arcgis.com/home/item.html?id=a378b48be11b45b5bb25254643304cb7
– Mapperz♦
8 hours ago
1
1
Best practice is to only place the feature classes which are absolutely required to be in feature datasets together. It's an antipattern to use feature datasets as a folder to glom related data together; doing this slows the actual FDS operations with additional checking and locking.
– Vince
7 hours ago
Best practice is to only place the feature classes which are absolutely required to be in feature datasets together. It's an antipattern to use feature datasets as a folder to glom related data together; doing this slows the actual FDS operations with additional checking and locking.
– Vince
7 hours ago
add a comment |
1 Answer
1
active
oldest
votes
No, a feature dataset is used to group related feature classes (see here). These feature classes can have related tables, but the tables will be stored outside the feature dataset.
One approach that I see with many organization is to have distinct database users / schemas / whatever to keep projects separated. This way, you don't need to have separate geodatabases, and it also gives you an easy way to implement security (e.g. when not all users are allowed to see all projects)
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "79"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fgis.stackexchange.com%2fquestions%2f318243%2fstoring-related-tables-and-toolboxes-within-feature-dataset%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
No, a feature dataset is used to group related feature classes (see here). These feature classes can have related tables, but the tables will be stored outside the feature dataset.
One approach that I see with many organization is to have distinct database users / schemas / whatever to keep projects separated. This way, you don't need to have separate geodatabases, and it also gives you an easy way to implement security (e.g. when not all users are allowed to see all projects)
add a comment |
No, a feature dataset is used to group related feature classes (see here). These feature classes can have related tables, but the tables will be stored outside the feature dataset.
One approach that I see with many organization is to have distinct database users / schemas / whatever to keep projects separated. This way, you don't need to have separate geodatabases, and it also gives you an easy way to implement security (e.g. when not all users are allowed to see all projects)
add a comment |
No, a feature dataset is used to group related feature classes (see here). These feature classes can have related tables, but the tables will be stored outside the feature dataset.
One approach that I see with many organization is to have distinct database users / schemas / whatever to keep projects separated. This way, you don't need to have separate geodatabases, and it also gives you an easy way to implement security (e.g. when not all users are allowed to see all projects)
No, a feature dataset is used to group related feature classes (see here). These feature classes can have related tables, but the tables will be stored outside the feature dataset.
One approach that I see with many organization is to have distinct database users / schemas / whatever to keep projects separated. This way, you don't need to have separate geodatabases, and it also gives you an easy way to implement security (e.g. when not all users are allowed to see all projects)
answered 8 hours ago
BerendBerend
2,625618
2,625618
add a comment |
add a comment |
Thanks for contributing an answer to Geographic Information Systems Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fgis.stackexchange.com%2fquestions%2f318243%2fstoring-related-tables-and-toolboxes-within-feature-dataset%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Geodatabase Diagrammer for 10X > arcgis.com/home/item.html?id=a378b48be11b45b5bb25254643304cb7
– Mapperz♦
8 hours ago
1
Best practice is to only place the feature classes which are absolutely required to be in feature datasets together. It's an antipattern to use feature datasets as a folder to glom related data together; doing this slows the actual FDS operations with additional checking and locking.
– Vince
7 hours ago