Re: SQL Server 2005 Cluster Setup Quiz
- From: "Michael Hotek" <mike@xxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 15 Mar 2006 11:02:22 -0600
LOL! This is definitely novel Ray. And very good as well.
Answers Inline
--
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"Ray Schueler[MSFT]" <RaySchuelerMSFT@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:411EC245-ED72-4F49-A21E-A6E58416A909@xxxxxxxxxxxxxxxx
This quiz consists of 10 multiple choice questions and 1 extra credit
question. This is an "open book" quiz. Feel free to use any resources at
your
disposal.
Feedback is welcome.
Ray
This posting is provided "AS IS" with no warranties, and confers no
rights.
------------------------------------------------------------------------------
1. Where is sqlserver.exe located for the named instance "STPNAMED"? This
is
the first instance on the cluster. (Assume the default directory is used.)
a) ..\Microsoft SQL Server\MSSQL$STPNAMED\Binn\sqlservr.exe
b) ..\Microsoft SQL Server\MSSQL.1\Binn\sqlservr.exe
c) ..\Microsoft SQL Server\MSSQL$STPNAMED\MSSQL\Binn\sqlservr.exe
d) ..\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\sqlservr.exe
E. Not necessarily any of the above. If you have installed Analysis
Services, it would be something higher than 1. The same goes for SSIS,
SSRS, SSNS, and anything else. Basically any of the feature check boxes
that are at the same level as the Database Engine will each generate a
directory that is .1, .2, .3, .N. I find this install behavior VERY
irritating regardless of whether it is clustered or not. My assumption is
that someone forgot to fix something that was hardcoded. Every time I've
been asked, why in the heck the directories are now named this way and
eveery single feature drops its own directory simply in the order in which
they were installed, I simply punt, because I can't think of any logical
reason at all to do this.
What would I want it to do....which is actually the real question..... C
2. How many cluster nodes does SQL Server 2005 Enterprise Edition support
on
x86, x64 and IA64 platforms?
a) Infinite
b) 8 nodes
c) 4 nodes
d) 2 nodes
:) Trick question, not fair. Which OS version and OS edition are you
installing the Enterprise Edition to. Pretty hard to support 8 nodes when
the OS you install it to will only support 2 or 4 nodes.
3. Where are the SQL Server 2005 setup log files found?
a) "\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG"
b) %temp%
c) ''\Program Files\Microsoft SQL Server\90\Shared"
d) %windir%
Mine are in D. They expected them to be in A.
4. What is the template.ini used for?
a) Diagnosing setup failures
b) Provide a template for unattended setup command lines.
c) Provide a template on how to read SQL Server 2005 setup log files.
d) Provide a template for writing stored procedures.
B. You might want better documentation for that since most people don't
know you can do this since you never could before.
5. When installing a SQL Server 2005 failover cluster, what service runs
setup on remote nodes?
a) Task Scheduler service
b) SQLSETUP service
c) Cryptographic service
d) SQL service
A. It should be B since that is really what should be controlling it.
6. How do you change the IP address of the SQL IP cluster resource after a
SQL Server 2005 failover cluster has been installed?
a) Run setup.exe from CD, select maintenance, select change IP.
b) Click on the SQL Server 2005 entry in Add/Remove Programs, select
maintenance, select change IP.
c) Uninstall SQL Server 2005 cluster, Reinstall with new IP address.
d) Change the IP in cluster administrator.
LOL! B. I should be able to do this through SQL Configuration Manager.
I've tried to do it in cluster admin and it hasn't always worked.
7. What is different about the remote setup dialog in SQL Server 2005
compared to SQL Server 2000?
Reminder: This is an "open book" quiz.
a) A login and password need to be entered for each node.
b) The remote setup dialog has been removed.
c) There is no change in the dialog.
d) Only the password of the logged-on account can be entered.
B
8. You select all components on the component selection dialog, including
SQL Server and Analysis Services to be installed as a failover cluster. On
your 2 node cluster, what components will be installed on both nodes?
a) Management Tools
b) All components
c) SQL Server Engine and Management Tools
d) SQL Server Engine and Analysis Services
D. It should be B and I've had 3 bugs filed on that which were closed
without getting it fixed.
9. What are 5 cluster specific command line options for unattended cluster
setup?
a) VS, INSTALLVS, IP, GROUP, ADDNODE
b) VS, INSTALLSQLDIR, TARGETCOMPUTER, ADDLOCAL, SAPWD
c) INSTANCENAME, IP, GROUP, CLUSTER, TARGETCOMPUTER
d) INSTANCENAME, ADMINACCOUNT, ADMINPASSWORD, IP, GROUP
Can't remember
10. How have the permissions changed on files and folders on the shared
drive of a SQL Server 2005 failover cluster installation?
a) SQL service accounts are given access to files and folders.
b) Local groups are given access to files and folders.
c) Local administrator access is removed from files and folders.
d) Domain groups are given access to files and folders.
D and it's about time. Windows security best practices.
11. Extra Credit:
Installation Order:
Instance 1 - Standalone default instance installed on node 1
Instance 2 - SQL Engine failover cluster named instance installed on nodes
1
and 2.
Instance 3 - Standalone named instance installed on node 2.
Where will sqlservr.exe be found in the default location of the 3rd
instance
on node 1?
a) ..\Microsoft SQL Server\MSSQL.1\Binn\sqlservr.exe
b) ..\Microsoft SQL Server\MSSQL.2\MSSQL\Binn\sqlservr.exe
c) ..\Microsoft SQL Server\MSSQL.2\Binn\sqlservr.exe
d) ..\Microsoft SQL Server\MSSQL.3\MSSQL\Binn\sqlservr.exe
E. Most likely .3, but it really depends upon whether all you installed was
the instance since every other top level feature increments the directory
name. See answer to question 1. Since this is a complete needle in a
haystack, how do I figure them out? I open Management Studio, connect to
all instances installed (standalone as well as cluster), figure out what .x
directory the stuff is in for a particular instance and then create a text
file that is placed in the Microsoft SQL Server directory that maps all of
the instances to the correct .x thingamadoodle. I also e-mail the text file
to all of the DBAs and sysadmins who have to deal with the server, print it
out and post it on the rack in the server room, and stick it on the wall in
my cube. Everyone involved is required to keep this text file up to date as
part of the installation routine as well as print out a new copy for the
rack in the server room and send an e-mail to everyone telling them that
something new was installed. (This is an interim solution until I can
figure out how to write the code to rename all of these things into a human
readable, understandable, and most importantly recognizable format.) On a
scale of 1 - 10, I would rate changing this one a 38, because it completely
interferes with every maintenance action that a DBA needs to perform as well
as making a complete mess when multiple instances are installed.
My extra credit back: I have a massive 32 proc machine with loads of
everything necessary. I install 8 instances of SQL Server 2005 along with
SSRS, SSIS, SSNS, and SSSAS on this machine. How do I find the SQL Server
errorlog for any given SQL Server instance without having to write them and
print out directory to instance name mappings?
.
- References:
- SQL Server 2005 Cluster Setup Quiz
- From: Ray Schueler[MSFT]
- SQL Server 2005 Cluster Setup Quiz
- Prev by Date: Do I need Enterprise to do clustering?
- Next by Date: Re: Do I need Enterprise to do clustering?
- Previous by thread: Re: SQL Server 2005 Cluster Setup Quiz
- Next by thread: Re: SQL transaction logs on iSCSI
- Index(es):
Relevant Pages
|
