In many cases we don't actually need the entire table structure to help splve a problem. Many times, only a subset of the columns are relevent to a problem and those are the columns that should be provided along with the PK and other indexed columns (and indexes) that may be a part of the current solution and/or could be used to help provide other solutions.

Sample data should be just that, sample data. Enough data to ensure that we understand the problem domain (should cover edge cases, data to be included in the solution and perhaps even data to be excluded). But not so much that is overwhelmes those trying to help.

And then the expected results based on the sample data. This is actually best shown using a table that is populated using INSERT INTO statements just like the sampel data is provided to populate the source tables. This serves two purposes. One, it gives us a visual of what the results should look like. Two, it actually provides something to test against.

Last, the code you have written so far in an effort to solve your problem or issue. This helps us to understand what you are trying to do and we may see a simple logic error that you have over looked (forest and trees syndrome) or we may come up with a totally different solution.

If some of these things seem like the may overwhelm your post, upload then as text files in a zip file instead.

A clear description of the problem and what you are attempting to accomplish is also very helpful.

The best thing to do is ask yourself, based on what I have posted could I provide an answer to problem based solely on what I have presented with no other knowledge of of the system I am working on. This will tel you if there is additional information that you should consider posting.

Please remember, we don't want production data or anything your company may consider IP or trade secrets.