Azure table design best practice

What's the best practice for designing tables in Azure Tables to optimize query performance?

Hi Raj,
When we design the azure table, we need to consider the scalability of the azure table.
and selecting the PartitionKey is very more important to scalability.
Basically, we have two options which have their advantages and disadvantages:
One Option: having a single partition by having the same value for PartitionKey for all entities to
Second Option: having a unique value for PartitionKey for every entity
More information about how to get the most out of windows azure tables ,please refer to the link below:
http://blogs.msdn.com/b/windowsazurestorage/archive/2010/11/06/how-to-get-most-out-of-windows-azure-tables.aspx
There is also a detailed article which explain how to design a scalable partitioning strategy for Windows Azure Storage,please refer to the link below:
http://msdn.microsoft.com/en-us/library/hh508997.aspx
Best Regards,
Kevin Shen

Similar Messages

Resources for from design - best practices for layout?

Hi,
I have made a number of forms fo the past few years. I feel like they look dated and are somewhat stale...   I have found a few resources out there on Javascript best practices and more mechanical focused articles, but nothing really specific design as it relates to usability and "feel". I realized some of this is subjective and varies depending on the form's purpose, but I am just looking for some new ideas.
Does anyone have a resource or listing of froms they think are outstanidng from a design perspective?
Is anyone willing to share forms they think are outstanding? Just that baisics like information collection?
How much color and line type objects become to much?
What are some design elements used in "web 2.0" (whatver that really means) that we sould be using in our forms. tempered with what can be done.
I am looking for this to be an open disucssion and am curious to hear what works for others. I hope others will find this interesting and helpful.
Cheers,
Tom

And the second snippet code validates any form to check every fields if values are not null, if a value is null it will setFocus on the first null field
2. Validate Form and Focus on First Field that Fails Validation
     2.1 Create a script Object with two small methods to return a table of fields that have null values
Script Object :
form1.#variables[0].myForm - (JavaScript, client)
//Tab for field's expressions and field's exceptions
var tabExpression;
var tabException;
function validateAllFields(rootObject){
          //If a field is null, stop everything
          if (tabExpression.length > 0)
                         return;
          //If the 'presence' property is by default 'visible' in the form and the object value is 'visible', the 'presence' property doesn't exist
          //If its default value is "hidden", the property always exist
               if (!rootObject.isPropertySpecified("presence") || rootObject.presence == "visible"){
                              //Verify if the object contains an interface 'button'
                              //The button is considered as a 'field', so if it's not a button the statement is true
                              if (!(rootObject.isPropertySpecified("ui") && rootObject.ui.nodes.item(0).className == "button")){
                                             //If the object contains nodes and if it's not a 'field' or a RadioButtonList
                                             if (rootObject.nodes.length > 0 && (rootObject.className != "field" && rootObject.className != "exclGroup")){
                                                            //Recall this method for each nodes in the object to find every fields (Recursive Method)
                                                      for (var i = 0; i < rootObject.nodes.length; i++){
                                                                                validateAllFields(rootObject.nodes.item(i));
                                             //Verify to add the object in the list if the object is a field and if it contains a value
                                             if (rootObject.className == "field" || rootObject.className == "exclGroup"){
                                                            if (rootObject.rawValue == null || rootObject.rawValue == 0){
                                                                           //Variable to determines if the object is an exception field
                                                                           var boValidate = true;
                                                                           //If there's exception fields
                                                                           if (tabException.length > 0){
                                                                                          //Verify if the field is in the exception list
                                                                                          if (tabException.indexOf(rootObject.name) != -1){
                                                                                                   boValidate = false;
                                                  //Add if the object is not in the exception table
                                                  if (boValidate)
                                                            tabExpression[tabExpression.length] = rootObject.somExpression;
     2.2 Create this method in your object as well, and will be called on a click_event
function getValExpressions(rootObject, tabExcption){
     //Create new table
     tabExpression = new Array();
     //Put the exceptions fields value in the exception table
     tabException = tabExcption
     //Validation
     validateAllFields(rootObject);
     //Return a null field
     return tabExpression;
     2.3 The click event is where you write the special validation for different forms
//Create a table with exception fields, can be used for special validation fields or no validation
var tabExceptionFields = new Array("dateField1", "txtComments", "txtTotal");
//Call the validation
var tab = myForm.getValExpressions(Main, tabExceptionFields);
if (tab.length > ){
     xfa.host.setFocus(tab[0]);
} else{
     var boValidate = false;
     var strExpression;
     //write your validation according to the fields you need special validation.
     if (statement == false){
          strExpression = Reference_Syntax.Field.somExpression;
          boValidate = false;
      if (boValidate){
          xfa.host.print(1, "0", (xfa.host.numPages -1).toString(), 0, 0, 0, 0, 0);
     } else{
          xfa.host.setFocus(strExpression);
I will post a form template as an exemple for these function
Enjoy!
Message was edited by: Magus069

Software Design best Practices

Background:
I have an existing J2EE web application in place with an Oracle 11 db and a WebSphere app server. The database is about 400 GB, has about 500 tables, and is usually processing about 35 db transactions per second. The average “web transaction” (submit) is about .21 seconds. The users are happy.
I have been the DBA on the project for many years and also largely architected much the application framework and design components.
I am having a debate with one of the developers about the best way to modify an existing page to meet some newly established business needs. I feel like I strongly know the answer to my question, but none the less our discussion is at an impasse and we need you help solve our debate.
Scenario:
There is an existing page in the application for client’s medical health profiles. This data is stored on MEDICAL_PROFILE. This table has 2 children: DOCTOR and MEDICATION. Of course a profile may have many doctors and many medications. The medical profile table has 30 columns on it.
The change request is to add another tab on the page with about 40 more data fields and to expand the existing page by additional 50 data fields.
Option 1:
For me, I simply wanted to add these new columns to the MEDICAL_PROFILE table, as these are logically attributes of the profile itself (a one-to-one relationship) and this would be consistent with the way we do things in our other application areas. This would put about 120 columns on the table.
Option 2:
The developer prefers the object oriented approach. The developer is of the mindset that these new columns should go on a separate small tables. She agrees that they are attributes of the profile, but since they are presented on the different tab or in different profile's boxes they can be divided and the smaller logical chunks.
Further she thinks that with a new tables, this will lend itself better to creating new and separate java objects that can plug-and-play elsewhere the application for code reuse should these objects ever be used in other places.
She further finds that 120 columns on the table is really too much for ease of development – you can’t easily view or keep in mind a huge object with more than 250 getter/setter methods. She prefers small objects for better reusability and maintainability.
The question:
Who is right? What option is the best practice for an object oriented application on an RDBMS?
Thanks.
L and S

LC wrote:
The change request is to add another tab on the page with about 40 more data fields and to expand the existing page by additional 50 data fields.
Option 1:
For me, I simply wanted to add these new columns to the MEDICAL_PROFILE table, as these are logically attributes of the profile itself (a one-to-one relationship) and this would be consistent with the way we do things in our other application areas. This would put about 120 columns on the table.Although you haven't provided evidence to defend the relationship, if you are correct, then I agree that they should all be associated with the MEDICAL_PROFILE table/entity. It's crucial that the data model be correct for many, many reasons.
>
Option 2:
The developer prefers the object oriented approach. The developer is of the mindset that these new columns should go on a separate small tables. She agrees that they are attributes of the profile, but since they are presented on the different tab or in different profile's boxes they can be divided and the smaller logical chunks.
Further she thinks that with a new tables, this will lend itself better to creating new and separate java objects that can plug-and-play elsewhere the application for code reuse should these objects ever be used in other places.
She further finds that 120 columns on the table is really too much for ease of development – you can’t easily view or keep in mind a huge object with more than 250 getter/setter methods. She prefers small objects for better reusability and maintainability.
Why does there have to be a one-to-one Java object to database table mapping?
What about using Object Relational Views to present different objects to the caller but keep the data model correct but allow for the developer's preferred approach?

Varying table columns, best practices

I've been wondering about this for quite sometime now. JTable is very complex, but it has a lot of funcationality that hints at reusable models. The separation of TableModel and ColumnModel seems to hint at being able to reuse a TableModel that stores some sort of objects, and apply different ColumnModels to view the data in different ways. Which is really cool.
However, who is in charge of managing the columns? The default implementation is usually good enough. But, it doesn't do anything special to the columns like: assign renderers, or editors. Should the column model be in charge of this? But, then you have to swap full on column models out when you want to change the look of the table. What if you just want to vary the renderer on a column, or remove one column. Would you build a whole new ColumnModel for this?
Should the JTable be in charge of setting himself up in these matters? But that seems to impose the view's representation on the model. What if you change views in some way that affects your model's structure.
Should there be some external controller in charge of this?
Sometimes you don't plan for these things at it hurts you when you need to reuse models, but maybe modify them in some way. What are your best practices?
charlie

The practice you described is what I'm doing right now, and I feel that it is cumbersome for reuse.The practice you described is what I'm doing right now, and I feel that it is cumbersome for reuse.
What I'm wondering is that if anyone has come up with a very elgant way to organize their class' responsibilities between who populates the column model. I know I can subclass and fill it in the subclass, but it seems that I might NOT need to subclass, use the default, and have another class ( maybe the JTable or a controller ), that populates the ColumnModel.
Then I can get better reuse between TableModel's and ColumnModels.
charlie

Table partitioning best practices

Just looking for some ideas.
We have a large information warehouse table that we are looking to partition on 'service_period' id. We have been requested to partition on every month of every year which right now will create approximately 70 partitions. The other problem is that this is a rolling or dynamic partition meaning we will have a 'new' partition vale with each new month. I understand in 11g there is a rolling partition functionality but we are not there yet.
So right now we are looking for a best practice for this scenario. We are thinking of possibly creating a partition on each year and indexing on the service period within each partition, maybe hash partitioning on the service period id (although does not seem to group the service periods distinct within each partition), somehow creating the partition dynamically via pl/sql (creating the table with a basic partition and then running an alter table on the data creating the proper number of partitions within a list partition.
I am also wondering if there is a point of too many partitions on a table. I am thinking 70 may be a little extreme but not sure. We are going to do some performance testing but would be nice to hear from the community. We have 5,000,000 over approx 70 partitions giving us approx 70,000 records per partition. The other option would be to create the partition based on year and then apply an index over top on the service period to reduce the number of partitions.
Thanks in advance,
Bruce Carson

This is not a lot of data, so the effort of partitioning may not be worth the benefit you receive. 70 partitions is not unreasonable. Do you have performance problems ? Do the majority of your queries reference service_period ? Do you have a lot of full table scans ?
Partitioning strategies depend on the queries you plan to run, your data distributions, and your purge / archival strategy.
Think about whether you should pre-create partitions for years in advance. Think about whether you should put every partition in a seperate tablespace for easy purging and archival. Think about what indexing you will use (can you use local indexes, or do you need global ?) Think about what data changes are happening ? Are they all on the newest data ? Can you compress older partitions with PCT_FREE 0 to improve performance ?

The Design - Best practice

hello all
I need help in design in (AD) and SCCM 2012
my topology is :
central site (HQ) and (16) branches
each branch have around 15 users , and connected via IP-VPN to central (HQ )
I cannot make additional domain or even RODC in the branches for some causes
I just organized them by create OU for each branch
My Question : what's the best practice to organize and manage those branches (in domain controller
and in sccm) for my case.
thank you all

You not really giving a lot of details but bases solely on what little details that you have given, a single primary site leveraging branch cache will be all you need.
Garth Jones | My blogs: Enhansoft and
Old Blog site | Twitter:
@GarthMJ

Questions VLAN design best practices

As per best practices for VLAN design:
1) Avoid using VLAN 1 as the “blackhole” for all unused ports.
2) In the local VLANs model, avoid VTP (use transparent mode).
Point 1
In a big network, I'm having VLAN 1 as the blackhole VLAN. I'd like to confirm that, even if we're not complying with best practices, we're still doing fine.
a) all trunk ports on all switches have the allowed vlans explicitly assigned.
b) about all ports on all switches are assigned to specific data/voice vlans, even if shutted down
c) the remaining ports (some unused sfp ports for example) are shutted down
d) we always tag the native vlan (vlan dot1q tag native)
So, no data is flowing anywhere on VLAN 1. In our situation, it is safe to use VLAN 1 as blackhole VLAN?
Point 2
Event if we're using local VLANs model, we have VTP in place. What are the reasons of the best practice? As already said, we allow only specific VLANs on trunk ports (it's part of our network policy), so we do not have undesired layer 2 loops to deal with.
Any thoughs?
Bye
Dario

We are currently using VTP version 3 and migrating from Rapid-PVST to MST.
The main reason for having VTP in place (at least for use) is to have the ability to assign ports to the correct VLAN in each site simply looking at the propagated VLAN database and to manage that database centrally.
We also avoid using the same VLAN ID at two different sites.
However, I did find something to look deeped: with MST and VTP, a remote switch can be root for a VLAN it doesn't even use or as active ports into, and this doesn't feel right.
An example:
1) switch1 and switch528 share a link with allowed vlan 100
2) switch1 is the root for instances 0 and 1
4) VLAN 100 is assigned to instance 1
5) VLAN 528 is not assigned to any particular instance so it goes under instance 0
6) VLAN 528 is the Local Data LAN for switch528 (switch501 has VLAN 501)
swtich528#sh spanning-tree vlan 528
MST0
Spanning tree enabled protocol mstp
Root ID Priority 24576
Address 1c6a.7a7c.af80
Cost 0
Port 25 (GigabitEthernet1/1)
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Bridge ID Priority 32768 (priority 32768 sys-id-ext 0)
Address 1cde.a7f8.4380
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Interface Role Sts Cost Prio.Nbr Type
Gi0/1 Desg FWD 20000 128.1 P2p Bound(PVST)
Gi0/2 Desg FWD 20000 128.2 P2p Edge
Gi0/3 Desg FWD 200000 128.3 P2p Edge
Gi0/4 Desg FWD 200000 128.4 P2p
Gi0/5 Desg FWD 20000 128.5 P2p Edge
switch1#sh spanning-tree vlan 501
MST0
Spanning tree enabled protocol mstp
Root ID Priority 24576
Address 1c6a.7a7c.af80
This bridge is the root
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Bridge ID Priority 24576 (priority 24576 sys-id-ext 0)
Address 1c6a.7a7c.af80
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Interface Role Sts Cost Prio.Nbr Type
Should I worry about this?

Webi: BW Query design best practice question

The scenario is as follows:
SAP NetWeaver BW 7.01 SPS3
Business Objects Enterprise XI 3.1 Fix Pack 1.2
SAP Integration Kit XI 3.1
Webi report built off of a BW Query. Based on the versions listed above, the MDX statement generated should only pick up only the fields listed in the query panel in Webi, not necessarily every field in the underlying BW query. Having said that, does it matter what fields are in the Free CHAR or in the rows in the underlying BW Query?? I heard a suggestion that all fields should be put in the Free CHAR panel of the BW Query Designer but I don't see the value add of that approach. Any thoughts?
-Brad

Hi,
it does not matter if the items are Free Characteristics or rows or columns.
for best practices here some material:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/008d15dc-f76c-2b10-968a-fafe5a121129
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/b0320722-741c-2c10-afab-93b5c0fc7e96
Ingo

MPLS Design Best Practices for SP

When deploying a new MPLS backbone for a Service Provider, what will be consider the best practices in general? For example what about the following list and any other items:
- Define the Internet as a VRF?
- Use private ASNs?
- Define a VRF per special service?
- Use at least two route reflectors?
- Use OSPF as IGP?
- Limit the CE-PE routing support to OSPF and BGP?
What will be the best approach for management of the devices? A management VRF or the nodes to natively be on a management network?
What to consider when designing from scratch?

William some recommended practises, although you can point out your specific constraints in adopting any.
- Define the Internet as a VRF?
(Yes Logical speperation is the way to go.)
- Use private ASNs?
(No, use a Public AS, you may have to peer outside your AS in a VRF with other AS's)
- Define a VRF per special service?
(This is Perfect , Logical Seperation)
- Use at least two route reflectors?
(Right, atleast 2 and above that depends on the size of your network)
- Use OSPF as IGP?
(I dont see any problems with OSPF in scaling for big networks)
- Limit the CE-PE routing support to OSPF and BGP?
(This aspect shouldnt impact much really, you can very well support all the protocols, as its more of serving your customers, rather than dictating the conditions.
Yes have a seperate VRF for Device Managements (also give a thought for a management subnet, which would be unique across your network)
You should generally start with a overview topology, introdcution of the objectives. And then go ahead with the suggested phy topo,
And then move on to the logical services, beggining from Core IGP, then core BGP, and then all the add on protocols, multicast , MPLS TE etc/. Then you can cover specilized service and their logic and description in the end.
Pretty much, just simply think of building out right from scratch that is Physical Layer and Move to Layer 2 and then Layer 3 Layer 4 .
So basically you doc should be index in a manner following the sequence of the OSI layers, this gives a good flow to the doc. And rest remains is the description of the logic used in each service or deployment method, that would be your skill.
HTH-Cheers,
Swaroop

Universe Design Best Practices for Oracle

Hello All,
We recently moved from XIR2 on MS SQL 2005 to XI 3.1 on Oracle. This has been a difficult move for us as my team is new to oracle. I'm currently working on several performance issues between BOBJ and Oracle and am looking for documentation on best practices for universe design with oracle. I've foudn tidbits here and there regrading using parameters joing_by_sql and boundary_weight_table, wondering if there are other options out there that might help. We have queries taking 45+ minutes to run and that is totally unacceptable.
thanks
Andrea

I am not sure if you are looking for Optimization or anything else. sorry for that following link might help you considering Oracle as DB.
Link:[Universe Optimization 1|http://www.bidwtoday.com/business-objects/universe-designer/business-objects-universe-optimization/]
Link:[Universe Optimization 2|http://forums.sdn.sap.com/post!reply.jspa?messageID=8721932]
--Kuldeep

Portal Design - Best Practices for Role and Workset Tab Menu

We are looking to identify and promote best practices in SAP Portal Design.
First, is there a maximum number of tabs which should exist on the highest level tab menu, commonly called the role menu? Do a large number of tabs on this menu cause performance issues? Are there any other issues associated with a large number of tabs on this menu?
Second, can the workset tab menu be customized to be 2 lines of tabs? Our goal is to prevent tab scrolling.
Thanks

Debra,
Not aware of any performance issues with the number of tabs in the Level 1 or 2 menus, particularly if you have portal navigation caching enabled.
From an end user perspective I guess "best practice" would be to avoid scrolling in the top level navigation areas completely if possible.
You can do a number of things to avoid this, including:
- Keep the role/folder/workset names as short as possible.
- If necessary break the role down into multiple level 1 entry points to reduce the number of tabs in level 2.
An example of the second point would be MSS. Instead of creating a role with a single workset (i.e. level 1 tab), we usually split it into two folders called something like "My Staff" and My Finance" and define these folders as entry points. We therefore end up with two tabs in level 1 for the MSS role, and consequently a smaller number of tabs in level 2.
Hope that helps......
Regards,
John

GUI Design Best Practices

Still learning Java and OOP. The question is, what is the best practice method for designing the user interface? For instance, I have a main_GUI that has all the basic stuff and then I need to have 5 or so different displays. A couple of them need to be modal so I'm creating those as jDialog. Is this correct or should you not use those.
Actually, all of the additional screens I want to be modal so I don't see another way of creating a normal jFrame that is modal which is why I'm asking before creating every screen as a jDialog.
Also, I have one screen that could have 3 different functions. Is it acceptable to create the screen with all of the components and just hide the ones that I don't need at any given time or should I actually create 3 different screens that all look roughly the same?
Thanks for any input/advice.

ShosMeister wrote:
So what's the difference, or more importantly, what's wrong with using jFrames? If you are creating a stand-alone, non-web app, then you will of course create a JFrame, and place your app in it, but I'm suggesting that the app not extend JFrame but rather you simply create a JFrame when you need it, and place a JPanel in this JFrame's contentPane, pack it and display it. The reasons for not extending a JFrame are multiple but mostly boil down to a general preference to avoiding extending classes with inheritance and using instead composition. There are many blogs dedicated to discussing this paradigm which can be found with Google, and here are two decent articles from the first page of my search:
[JavaWorld: Inheritance versus composition: Which one should you choose?|http://www.javaworld.com/javaworld/jw-11-1998/jw-11-techniques.html]
[Object Composition vs. Inheritance|http://brighton.ncsa.uiuc.edu/~prajlich/T/node14.html]
One error caused by extension of a Swing class via inheritance that I saw in a recent thread in the Swing forum involved a class that overrode JLabel and held x and y int variables. The class had setX(int i), setY(int i), and getX(), getY() methods and thereby unknowingly overrode JComponents own similar methods completely messing up the JLabels ability to be positioned correctly.
Are you saying I should only have one "window" and swap the data constantly in that window? Nope. I am saying that you should emulate other windows-like programs that you use. Most use a combination of panel swapping, modal and non-modal dialogs, ... whatever works best for the situation. But most importantly, you should write your code so that it is easy to change from one to the other with a minimal change in your code. Aim for flexibility of use.
Would that require that all the jPanels were the same size to be able to display correctly?If you swapped with a CardLayout and created your JPanels to be flexible with sizing, the CardLayout would take care of this mostly for you.
So if I create a main jPanel, set it up with all of the components that I want, when I run the program and main() is called, it would create the jFrame and drop the jPanel into itself? Not sure I've seen any examples of that so I'll have to look that one up. Yes, you'd drop the JPanel into the JFrame's contentPane. There are plenty of examples here, but it may take some digging to find them.
Unless of course I've completely misunderstood you which is possible since, as I've mentioned, I'm just learning Java.I think you are understanding what we suggest here. You are asking the right questions, so I predict that you should learn Java quickly.
Thanks!!!!Welcome!

PL/SQL Design: Best Practice

Hello everybody,
I'm trying to improve myself acquiring compentence in PL/SQL design. At now I am (or I wish to be) a good practitioner but I have to complain myself for lackings in designing architecture.
I mean, for example, how to organize procedure and functions in a package, how to use pattern architecture, logging and testing practices...
Do you know where I can find resources for these arguments? Which books do you suggest to start with?
Thank you very much.
Nicola

The best practices are the very same fundamentals that apply to all other languages and have existed for since the dawn of programming.
The single biggest fundamental principle is to modularise your design and code. A well designed program consists of building blocks. Different languages have different names for these - procedures, functions, units, packages, methods, routines, etc.
A program lives or dies by how well it is modularised.
If you only get that right, you can claim to be a Programmer and not a mere two bit developer.

UI Design - Best Practice when Two UIs Trigger Same Event

I have an application that allows users to take actions using several methods - right-click context menu selection, menu bar selected, key strokes, etc. I was wondering if anyone had any suggestions as to teh best practices for handling this in Cairngorm...
Is it best to dispatch the same Cairngorm event in several places? I know this is one of the major reasons to use MVC, but, I hate to create duplicate code - maintenance is pain.
Would is be considered good practice to have the container that serves as a parent for the context menu, menu bar, etc. to listen for events from these components, and then dispatch the Cairngorm Event?
Thanks.

Would it be considered good practice to have the container that serves as a parent for the context menu, menu bar, etc. to listen for events from these components, and then dispatch the Cairngorm Event?
Yes, this is described by Steven Webster in his series of articles on Cairngorm.
Dispatching the same Cairngorm event from different locations is a perfectly regular practice. This is even an advantage. The same code (the command, the delegate) can be triggered from different places.

Bpm Design best practice

Hello Dear Co designers :)
what would be the best practice for desiging the follwing:
1- User can select the process insance distination form a drop down list [list of departments|http://forums.oracle.com/forums/] in the form (i.e. routing based on a desicion form the Form data)
2- user can add up to 4 departments in the input form to which process instance has to be routed to.
in other words i have this delima
3- Can i route the instance to the same role but with deferent departments?
for example i want only the users with role A but under organization unit B to see the instance in their inbox but users with role A under other org units cant see it??
is this possible??

You can use parametric roles to achieve this.
You must declare an instance variable called department and a parametric role where the paramater is the department. The partcipants will be assigned to the role with the specific parameter and the instance variable has to be assigned to a department, in this case automatically the instances will be routed by department.
Hope it helps

Azure table design best practice

Similar Messages

Maybe you are looking for