Installing Windows Server in preparation for SQL Server

Topic

New Reply

Hi,

Im interested in setting up a dba training environment at home. I have a few years developing reports in ssrs and Im interested in becoming a dba. I have installed sql server 2008 r2 at home in the past but now want to install it on windows server to get more familiar with admin duties, active directory, etc.

I don’t have any experience with Windows Server. Can anyone give me some advice on how I should install it knowing that my intentions are to install sql server on it next? Do I need to set windows server up as a domain controller, forest, etc?

Also, I have access to windows server 2008 R2 and Windows Server 2012. Which one should I go with? Seems like most companies are still using server 2008 r2 still…

Thanks in advance for any help

Reply | Quote

Replies

Are you sure you are ready for such a big leap? AD isn’t required for SQL and it doesn’t really provide any additional features apart from integrated authentication. I’d install a stand alone 2008R2 server and then SQL, but you can use 2012 if you want to see what it’s like. Having said that SQL installer does create AD permission groups and as a DBA you need to know about them.

I’ve found the biggest headache in SQL server as a DBA is remembering to check/fix job owners when you create maintenance jobs / DB tasks. The jobs are created under the currently logged in user, but that user may not have permission on the DB to perform the required actions. To fix it I tend to use SA as the job owner for backup tasks. (You should always create SA and AD accounts when installing SQL, just in case, and use a password manager to create / save the SA password.)

cheers, Paul

Reply | Quote

I tend to agree with Paul on this. If you install 2008R2 or 2012 and then get stuck into learning AD, you could be diverting your learning resources and / or capacity away from learning how to manage SQL instances in order for you to master AD. By the time you realise it you will have trained yourself to be a SysAdmin rather than a DBA.

Yes, there are some commonalities – but the people that can master both at the same time are talented and highly experienced.

While working as a SysAdmin, I encounter and work with various SQL databases daily, but I often have to refer to my documentation, or other sources. I don’t consider myself to be a DBA, rather a SysAdmin that can keep a lid on the SQL when needed.

My experience of DBA colleagues is likewise: they can manage a server and can interact with AD if needed, but usually only venture far enough to get their task at hand done.

There is no harm in running through some of the Technet virtual labs in AD to familiarise yourself, but if you are interested in becoming a DBA, I would recommend not to get too bogged down in Domain Administration tasks at the outset.

Reply | Quote

Don’t you usually agree with me?

cheers, Paul

Reply | Quote

Only when I’m right…..

:rolleyes:

Reply | Quote