Twitter

Follow SQLQuill on Twitter

Subscribe

MN Pass

Weekly Challenges 1/30/09

Here’s what I’ve been working on this week

  • We’ve added a new SQL server to our staging environment that has a database for archived data.¬†
    • Spent a bit of time troubleshooting the deployment process of this.
    • Added four part names to synomyns that need to use a linked server to get to the archived data
    • Identified and disabled triggers that aren’t needed in the archive process to increase performance
  • Coordinated building and QAed our Prod-Staging servers for our US Site
    • Five clusters and two stand alone servers built, configured and QAed by other members of my team
    • Production databases restored on them
    • Our code deployed to our new release
  • Coordinated building and QAed our Prod-Staging servers for our non-US Site
    • Five stand alone servers built, configured and QAed by other members of my team
    • Production databases restored on them
    • Our code deployed (different rev than US site) to our new release
    • Applied SQL2005 SP3 to these
  • OnCall for production
    • Deadlocks on our Transaction Log backups for log shipping with¬†LiteSpeed
      • Task completes successfully, but gives the deadlock error.
      • Altered Scheduling – reduced the problem, but didn’t fix it.
    • One of our database’s files (which is 700GB) became over 90% full, so I needed to expand it.

Leave a Reply

  

  

  

You can use these HTML tags

<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>