Skip to main content

MS SQL: How to change the table schema

Honestly I am not a DBA and it scares me to dead, when I have to write or run MS SQL administrative level scripts. I was having too much issue with a production backup and restore because some tables were user schema based and each time on staging; I had to delete and recreate tables with right schema. Today, I finally decided to change the schema of three tables which were giving me headaches on the live site. As the tables were created with a user name schema; I couldn't delete the tables as they have live data nor I knew how to change the schema.

After finding a solution on MSDN, I decided to modify and run it on the production server after some testing and review on staging. Below is the script that I have used. It is just a one-liner but it removes the hassle that was giving me too much grief over permissions and ownership.

ALTER SCHEMA MyNewSchema TRANSFER oldSchema.TheTableName

Happy Coding!


Popular posts from this blog

Working hours in six months to a year

I usually try to look for how many hours I have worked on a given project and what hours that I  spend on learning or network management tasks.

Below I have added some hours calculation, after finding the breakdown by months from Berkeley website.


2017Working hours six months (Jan 1st - Jun 30th): 
130 days x 8 hours =  1040 hours

Working hours six months (Jul 1st - Dec 31th): 
130 days x 8 hours =  1040 hours

Working hours for the year:
1040 hours + 1040 hours = 2080 hours
MonthWorking Days in the monthMonthly Working Hrs1/2 of working hrsMidpoint of working days in the monthDates of HolidaysJanuary22176888 a.m. 1/172,16February20160808 a.m. 2/1520March2318492Noon 3/1631April20160808 a.m. 4/17May2318492Noon 5/1629June22176888 a.m. 6/16July2116884Noon 7/174August2318492Noon 8/16September2116884Noon 9/154October22176888 a.m. 10/17November22176888 a.m. 11/1610,23,24December21168…