Monthly Archives: July 2013
Having used SQL Server Migration Assistant for a major Oracle conversion project over the last year, I quickly grew aggravated with its project limitation involving a single database. In other words, if you setup the project file in SSMA for staging and then you are unable to point it to an acceptance environment to migrate to that environment. That can be very frustrating especially if you have customized many of the project settings. I have discovered two workarounds to resolve this problem.
- Backup (or copy) the project folder (c:\Users\<<Username>>\Documents\SSMAProjects\<<Project Name>>). Close SSMA and then delete the target-metabase.mb file in the project folder. Now open SSMA and now you can connect to a new SQL Server and/or database. You would want to copy the folder if you want to retain the settings for a different environment such as staging, acceptance, production, etc. If you rename the folder for a different environment, make sure to rename the *.o2ssproj file to match the folder name. This is the file that opens inside of SSMA.
- The second option is to create a new project using SSMA and then copying in the object-containers.mappings, project-container.mappings, and finally preferences.prefs. These are the project settings that you have painstakingly setup in your original project.
I hope this helps. Enjoy!
What motivates you? Every time I think about work and motivation, I am reminded of the quote from Office Space:
Peter Gibbons: The thing is, Bob, it’s not that I’m lazy, it’s that I just don’t care.
Bob Porter: Don’t… don’t care?
Peter Gibbons: It’s a problem of motivation, all right? Now if I work my ass off and Initech ships a few extra units, I don’t see another dime, so where’s the motivation? And here’s something else, Bob: I have eight different bosses right now.
Bob Slydell: I beg your pardon?
Peter Gibbons: Eight bosses.
Bob Slydell: Eight?
Peter Gibbons: Eight, Bob. So that means that when I make a mistake, I have eight different people coming by to tell me about it. That’s my only real motivation is not to be hassled, that and the fear of losing my job. But you know, Bob, that will only make someone work just hard enough not to get fired.
I see this all the time. When I started at my current position and I worked hard on projects, everyone said: “Why bother, it’s not going to get you anywhere.” After working here for two years, I am starting to understand that logic sadly enough. However, It goes against how I was raised.
In addition, money is the ultimate motivator, but not the only motivation. For me it is growth, I am not out to break the bank. But, I do want to be acknowledged with regular raises. I personally need something to work for, a goal whether it be financial or a clear path for potential growth. Currently I have reached a glass ceiling, there is nowhere to go and without raises, I must rely on personal motivation. Yet, everyone around me is performing less and less due to the lack of motivation. It is difficult not to become Peter Gibbons. Maybe it is time to move on? However, I must fight to remain motivated.
How do you account for your databases? Do you track them in a database? If so, what information do you track?
I have a spreadsheet that hopefully I do not forget to update when I add a new database to a server so I know who to notify in case there are issues. When I took over this position there was very little information for most of the databases in my charge. I thought to myself ‘shouldn’t you know what each database is for and why it is on your server? How did it get there? Is anyone still using it?’ As database administrators I believe we should know our data.
I am interested to hear how others handle this and if you even care? Please send me your input. Enjoy!