Latest Contributions by MarceloMarques

yes, it is expected and known the data will take more disk space when it is loaded into SDE. You can improve performance using SQL Server Page Compression, create the empty featureclass schema, enable page compression on the tables and indexes, then load the data using ArcCatalog Simple Data Loader, also you can have a custom SDE DBTUNE to separate tables and indexes into different filegroups, large featureclasses like "contours" can have its own SDE DBTUNE keyword with its own filegroups/datafiles that are completely separate from the rest of the data, you still need to tune and maybe rebuild the spatial index after you load the data to make sure you get the best drawing performance possible, another thing to consider is table partitioning and index partitioning, you can implement SQL Server partitioning to improve performance, also when loading data on large featureclasses if the datafiles are in autogrow then this will cause lots of fragmentation, then consider to run dbcc shrink database, or resize the datafiles before you load the data to avoid heavy fragmentation, now all these best practices will help you improve disk I/O, but still at the end of the day your database storage plays a crucial role in I/O, you might find that even after implementing the best practices that the storage does not scale up and you need to consider a faster storage for your database datafiles, this can be determined if you run SQL Profile traces when the data is drawing in ArcGIS to find the slow queries and by analyzing the SQL Query PLAN you can get more info about the storage performance. Also the version of SQL Server plays an important role in performance, if you are using SQL Express then you cannot expect it to scale up with very large featureclasses, and the advanced features like SQL Server Page Compression requires SQL Server Enterprise Edition. I hope this helps.  ... View more

Yes, in a file gdb you have no option, you have to use the ArcCatalog tools. ... View more

You can make changes to the sequence and increase for example the cache sequence values in the RDMBS using SQL. ... View more

The best practice to separate tables and indexes applies for virtual and SAN storages. I talk more about this in my best practices guides books, check it out Mapping & Charting Solutions (MCS) Enterprise Databases Best Practices. In particular this might be of interest DBTUNE configuration keywords and disk configuration. ... View more

I am a very experienced Geodatabase Administrator that has been using DBTUNE for over 20 years, this idea is to bring that forgotten knowledge back into the current documentation and to continue to provide a dbtune template file that is so useful for the geodatabase administrators. I talk more about this here "Mapping & Charting Solutions (MCS) Enterprise Databases Best Practices".  ... View more