>I many of my parent-child table schemas, I have a column on the child table to indicate the "order" or "sequence" that the child record is in relative to the other child records of the same parent. It is an integer field and the first record is 1, then 2, then 3 etc.
>
>I have begun "upsizing' my databases from FoxPro to Sql Server, using the Upsizing Wizard in VFP9, and have tables where this field is named 'order', and it is getting named '[order]' when if gets pushed over.
>
>I want to rename it because I do not want my column names to have brackets around them.
>
>It's obvious why SQL Server needs to do this, but I just want advice or ideas on on choosing a smart name for this column. Surely everyone has similar structures in their data schemas.
>
>P.S. I also have the same problem for my columns named 'desc', which was intended to stand for 'description', but it is getting named '[DESC]'. For that one, I am planning to rename the column to 'description'.
>
>In VFP, these column names never caused my any problems, but as I prepare my data for life in the .NET and SQL Server world, I see that this needs to be addressed.
>
>So... suggestions for this column name please.

Seq, SortOrder, Ordinal (although this last one might be reserved in MS SQL Server, I don't know off-hand).

If this column represents the order in time in which the child items were entered, you could use a DateTime column (e.g. DateTimeCreated), rather than having to manage your current integer values.