Unfortunately, I missed “Meme Monday” yesterday. It’s a day late but hopefully no one minds. 🙂
This one was a bit difficult for me to write since I try to be more of a “the glass is half full” type of person. I try to be anyway. So here are some SQL Server problems I’ve experienced. I’ve included some from a past job as well. Note: the following are not in any particular order.
- GUIDs as part of database name
- Crystal Reports 8.5
- Trying to remember how to code efficiently in SQL Server 2000. Oh that’s right! Can’t do CTEs! Drat!
- Database servers deciding to reboot themselves for no apparent reason. Turned out to be hardware issue.
- Trying to find/make time to keep up with newer versions of SQL Server.
- Finding out one department was allowed to have their database objects in the master database on a cluster. Found out the hard way when I started removing the objects.
- “We need you to install SQL Server on these servers.” “Okay. Did someone buy the licenses for SQL Server?” “No. We need licenses?” “Um, yeah.”
I can’t help it. Call me silly, but I have a need to end this post on a positive note. So here are some good things I’m fortunate to have. 🙂
I Got 99 Treasures: I’m fortunate…
- to be part of a great team… we have each other’s back and there’s rarely a dull moment around here.
- to be a part of the awesome SQL Server community… there is a great deal of fantastic resources to tap into and terrific people who are willing to help.
- we have standards!
- to have developers who are willing to listen, learn, and collaborate.
- to have challenges. I hate being bored so I’m glad I have challenging work from time to time to help keep me busy and out of trouble.
- to have opportunities to learn new technologies and keep up with advances in SQL Server.
- we have source control and we all use it!
- to have an employer who believes in training.
- my team also likes dark chocolate. 😉