Re: Regarding MCDBA



"Derik Hinz" <DerikHinz@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:AE55C06C-AB56-456E-856B-72D77163D876@xxxxxxxxxxxxxxxx
The MCDBA is a Windows 2000 cert and does not focus on development.

I would take exception to this statement on two points.

[1] The MCDBA is not an OS-specific cert; it is specific to =SQL 2000=. It
can be achieved via electives from either Windows 2000, Windows 2003, or
..NET Programming.

[2] While the cert does not =focus= on development, you do need to be well
versed in T-SQL database query and basic use of SELECT/INSERT/UPDATE/DELETE
syntax. Specifically, exam 70-229 "Designing and Implementing Databases with
SQL 2000" requires this knowledge.

[3] Neither does the cert =focus= on administration, but you need to be well
versed in those skills typically performed by DBAs -- specifically those
addressed in exam 70-228 "Installing, Configuring and Administering SQL
2000"

If your
primary line of work is development in SQL, you will probably want the
2005
cert MCITP - Database Developer or MCITP - Business Intelligence
Developer.

I would also disagree with this statement.

Let me offer this alternative:
If your primary line of work has been =SQL 2000=, and will be for the
near future, you might want to consider completing the MCDBA and then taking
the upgrade exam to achieve any of the MCITP certifications (Database
Administrator, Database Developer, Business Intelligence Developer).

If your primary line of work is now =SQL 2005=, then you should focus on
the MCTS/MCITP certifications, as an MCDBA without the requisite =SQL 2000=
experience will be of no significant use.
Whether you focus on the MCITP:Database Administrator, or the MCITP:
Database Developer, or the MCITP: Business Intelligence Developer, will
depend on what specialities you focus on in your =SQL 2005= work.

--
Lawrence Garvin, M.S., MCTS, MCP
Independent WSUS Evangelist
MVP-Software Distribution (2005-2007)
https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E

Everything you need for WSUS is at
http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx

And, almost everything else is at
http://wsusinfo.onsitechsolutions.com
.....



.



Relevant Pages

  • Re: Dont understand what version of SQL to install
    ... Subscription and I still have to pay $49 to use SQL Developer? ... I don't think you have to buy another license for the Developer Edition, but you better ask this question to whom you bought it. ... it's not stated that SQL Server 2008 Enterprise Edition can be ... > So I can use SQL Developer 2008 to create a database in standard 2005, ...
    (microsoft.public.sqlserver.setup)
  • Re: Dont understand what version of SQL to install
    ... I'm talking about developing and testing databases for my client and ... To my XP, I can add SQL Developer 2008 to develop (I guess I should say, ... So I can use SQL Developer 2008 to create a database in standard 2005, ... installed on Client OSs such as Windows Vista. ...
    (microsoft.public.sqlserver.setup)
  • Re: Cool SQL Presentation At IDUG North America
    ... They have developer resources for just the kind of queries you are referring to, and show you how to place addresses on the Google Earth map. ... Cool SQL Presentation At IDUG North America ...
    (comp.databases.informix)
  • Re: Dont understand what version of SQL to install
    ... You can probably install it on Windows XP as well but I have not tried it yet. ... Actually, if you investigate the documents on Books Online, it's not stated that SQL Server 2008 Enterprise Edition can be installed on Windows XP nor Vista. ... I suggest you to use SQL Server 2008 Developer Edition to create databases for your SQL Server 2005 and 2008 database applications. ...
    (microsoft.public.sqlserver.setup)
  • Re: Dont understand what version of SQL to install
    ... I created a database using sql 2005 express edition. ... With that in mind - could you use SQL Server 2008 Developer Edition? ... installed on Client OSs such as Windows Vista. ...
    (microsoft.public.sqlserver.setup)