Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

6
  • blog.sqlauthority.com/2008/04/08/… Commented Jul 24, 2013 at 12:09
  • 3
    Why do you want to add it to that specific position? Commented Jul 24, 2013 at 12:12
  • just i gave example. I want to implement in another table.we need to follow uniform for all tables. Commented Jul 24, 2013 at 12:17
  • 3
    @user2354274 Order of a column in a table is not very relevant when retrieving information (except if you're using * everytime), so I still can't understand what forces you to do so. Please explain, I'm curious of the reason. Commented Jul 24, 2013 at 12:24
  • 2
    SQL Server doesn't support inserting new columns at a specific position in the table, nor can you move columns around. If you absolutely must have this, then you have no other choice than to create the new table with the correct structure (and order of columns) and copy over the data from the existing table Commented Jul 24, 2013 at 12:34