My Development Blog

SQL Server 2005 DBA

sheezy — Mon, 17 Aug 2009 23:13:37 +0000

About a month ago, I started working on my SQL Server 2005 DBA certification. The progress has been slower than I was anticipating. I’m studying on my own. I thought I would have more time at work and home to study, but I’ve been bombarded with work for the last two months.

Hopefully, I’ll be able to take at least the first test within the next month or two the latest. Wish me luck!!

MS SQL to MySQL

sheezy — Mon, 17 Aug 2009 23:10:19 +0000

I’m finally just about to go live with the project I’ve been working on for the past few months. On the development site, the dev SQL Server database is pushing data to the dev MySQL database. I setup the live SQL Server database to push data to a test MySQL database, just so I can make sure there isn’t anything funky on the live SQL Server database that I’m not aware of. Once I get the go ahead, the live SQL Server database will be pushing live data to the live MySQL database. When that happens, we gonnna parrttaaayy!! Just kidding.

Everything I’ve learned about MySQL and MS SQL during this project has been tremendous and will definitely help me on my way to becoming a real DBA.

MySQL four-part name

sheezy — Tue, 16 Jun 2009 21:52:21 +0000

All day I’ve been trying to use this four-part name to run queries on my linked server. All day…… Everyone seemed to suggest doing the four-part name instead of OpenQuery.
Every time I tried the four-part name, I would get this error:
“A four-part name was supplied, but the provider does not expose the necessary interfaces to use a catalog or schema.”

Of course when I found someone else with the same problem as me, they hadn’t found a solution. But…I finally figured it out. MySQL doesn’t support schemas or owners. So saying, LinkedServerName.DBName.Owner/Schema.TableName wasn’t working because it wasn’t supported. I’m too lazy to try to remember my search query that brought me to those forums of people with the same problem as me. Now, there won’t be an answer to their problem. Oh well.

Anyways, what ended up working for me was: LinkedServerName…TableName