After installing SQL server what thing we have to check

Question

Post reply

After installing SQL server what thing we have to check

rajeshjaiswalraj

SSCrazy

Points: 2574
More actions
June 1, 2014 at 10:06 am

#396844

After installing SQL server what thing we have to check.
1. As per security
2. General

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply

Koen Verbeeck SSC Guru Points: 259115 More actions · Answer 1

One of the first thing I'd check is that you can log in.

Then I'd set-up accounts, roles et cetera for other people to log in.

Then you can go over other things, such as setting the max memory limit, creating databases and so on.

Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP

MikaS Ten Centuries Points: 1210 More actions · Answer 2

rajeshjaiswalraj (6/1/2014)
After installing SQL server what thing we have to check.
1. As per security
2. General

I would suggest that you use your favorite search engine to find "SQL Server post installation checklist". There are many checklists out there you can use, either as they are or as a template to build your own.

Mika Sutinen, Senior DBA
@SQLFinn on Twitter
Blogging at SQLStarters[/url]

Jeff Moden SSC Guru Points: 1004414 More actions · Answer 3

To be honest, there are a whole lot of facets to consider for SQL Server AND Windows security. If you don't actually know what they are or your Yabigooglehoo doesn't lead to a good list (or don't know what a good list might consist of), you might want to consider hiring an SQL Server Security Consultant for a day or two.

For example, most security should be handled through Windows Integrated Security and there should be almost no individual logins. Almost everything should be handled through Windows Groups. There are things to consider with Firewalls, changing of the port that SQL Server responds to, deciding what the SQL Server login should be able to "see", disabling and possibly renaming the "SA" and certain other logins, ensuring that none of the sample databases were installed, setting up the Model database correctly, establishing backups and testing restores, establishing password policy, etc, etc, ad nauseum.

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)

Grant Fritchey SSC Guru Points: 398909 More actions · Answer 4

Security is just the start. I'd suggest modifying the cost threshold for parallelism. I'm just learning about modifying the system_health extended events session to only write to file and not to the buffer. There's max memory, ANSI default settings, collation, it's actually a pretty huge list.

"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt

Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning