Over at http://www.EllaBing.com they have a bow tie dedicated to us SQL DBA’s! Now how cool is that! They call it the Fragmented Index a fitting name if I do say so myself. Check it out!
Somehow I missed this. CTRL + ALT + T, go ahead press it. Wammo! All these lovely templates, to help us out! Templates, yeah nice, convenient, yes. But, what I like best, is you can add your own scripts! For as long as I can remember, I wondered where do DBA’s keep all their scripts? File Share? Bah, in my mind inconvenient, but alas, I delt with it, because I didn’t know any better. Not now my friends! I am slowly but surely putting all of my custom scripts into SQL Templates, and not looking back! A copy of all templates are placed in your user Documents and Settings folder under Application Data\Microsoft\Microsoft SQL Server\100\Tools\Shell\Templates.
Changing my Twitter handle has been in the back of my mind for some time now. brentk81 just didn’t have the charm, pizazz or descriptiveness I was looking for. In addition to the fact that my blog goes by the name of http://www.sqlrook.wordpress.com, I almost felt as if I had two separate personas I was trying to manage. One being this guy named Brent, trying to tweet about quasi relevant stuff, and the other being SQLRook, where I try my best to blog about SQL Server. But ENOUGH is ENOUGH! I’ve had it! I can’t take this much disorganization in my life! [JK] But still it was annoying. So I took the plunge breaking all the twitter rules of changing my handle name. I risked being ostracized by my piers…I risked it all for the glory of a name! And well, it was pretty unassuming, and it just made sense to have my Twitter account and Blog be known by the same name. Only one person on twitter even noticed… Jes Schultz Borland [Twitter | Blog], Thanks Jes! Oh, and I changed my pic…just keeping you folks on your toes!
So today I was attempting to delete a SQL account from one of my servers. Easy enough I thought, deleting the account from the server, check. I go to delete the account at the database level and BAM! I get the all too familiar evil red script!
Error: 15138 The database principal owns a schema in the database, and cannot be dropped.
So whats the error actually mean? Jump over to Derek Dieter’s awesome site SQL Server Planet to find out! I followed his script verbatim and it worked great for me!
First! I finally got the ‘interwebs’ at my new place in Jacksonville. I went about a week and a half without TV or Internet, phew that was rough…but not all bad, it just gave me the time to read more SQL books! This first post is about two weeks old, and will be my first post in a series of catch-up posts.
Another long week comes to an end. I’m sitting on a plane while writing this blog post, flying from Minnesota to Atlanta, then finally home to Jacksonville. With another disaster recovery test under my belt, I’m gaining more and more confidence in my abilities. This time I was able to meet my entire DBA team in Minnesota, it was great to finally put names with faces. I was finally able to get my hands on our replication schemes and get some good QA time in with the more Senior DBAs. I also greatly enjoyed being able to interact with the other DBAs on a more personal level. I was also able to meet most of the Server, SAN, and development teams. Project Managers, and Business Analysts, everyone that goes into a successful DR practice. Everyone from every team involved put in many long hours; it was a great experience, and an overall success. I’m greatly looking forward to our next exercise in February.
My first post of 2012 was a bit ambitious I admit. But I didn’t expect to trip up this quickly. So with that being said, I am still going to post as often as possible, making it a priority. Over the past few days, I finished out a busy work week, in which my company is prepping for a practice DR flip. Being so new, and having zero replication, mirroring, and log shipping experience, forced to shadow the more senior DBAs (which is just fine with me at this point). Yesterday was spent flying to Minnesota, and for a Florida boy, my goodness this is a cold state! Our practice flip was pushed back due to other IT technical difficulties. So as @SQLGator would say, the #sqlawesomeness starts tonight at midnight. In between recovering from 12-15 hour shifts, I will update everyone on how the DR flip went. I’m in Minnesota until Thursday afternoon, so I am hoping to have plenty to blog about, besides the cold weather. Cheers!
So I just recently accepted a new job in Jacksonville, FL, moving from the Tampa Bay area. It’s given me the opportunity to work with SQL 100% of the time. As to where my last position I had to split my time 50/50 as a System Administrator. Starting my new position has made me realize just how much I have to learn, and has truly made me feel like a rookie. I have been reading up as much as possible on replication and t-sql, so at least for the first part of 2012. I am going to concentrate my posts on those two subjects. I’d also like to start concentrating on SQL Server 2012.
And now for a few things:
- I’m excited to start attending the Jacksonville SQL Server User Group meetings and getting to know new people in the SQL community
- I’m excited to maybe hang out with @SQLChicken
- I really want to get my first SQL Certification this year
- I’d like to speak at a local user group meeting
- I’m sure there are more, and I will be updating this post through-out the week
Well that’s enough for now – cheers!
Okay, recently @SQLGator said he was going to make a resolution to update his blog once a day for 2012. I love his ambition, so much that I am going to try this feat. And that’s all I have to say about that, and for post number 1.
So as I am getting more comfortable with t-sql, I am trying to use the GUI less and less. Recently I had to restore a db to a DEV server. Good chance to use t-sql instead of the GUI!
RESTORE DATABASE adventureworks
FROM DISK = 'e:\adventureworks_backup_201107062202.bak'
No can-do sir! Error!
Error 3154: The backup set holds a backup of a database other than the existing database
hmmmm…OK, with a little research here is the resolution, a simple one at that!
Simply add the WITH REPLACE at the end of the RESTORE command! Its that easy!
RESTORE DATABASE adventureworks
FROM DISK = 'e:\adventureworks_backup_201107062202.bak