SQL Server | Planning an Installation

By -

“By failing to prepare, you are preparing to fail.”  

― Benjamin Franklin, Founding Father of the United States

 

Planning is usually the difference between a smooth road managing the SQL Server & a rocky one.

Things to consider:

  • Installation Requirements
  • Selecting the features
  • Scale up
  • Capacity Planning
  • Designing databases
  • Security
  • Core mode installation
  • Bench-marking tools


Installation Requirements

This steps is all about information gathering.

Let's identify all necessary components

Evaluate Installation

  • SQL components to install
  • SQL Server Edition
  • Operating System
  • Virtualization
  • Target Hardware

 

 

Scale-Up and Scale-Out

Gone are the days when someone could predict the Max database size, etc in an early discussion meeting.

Ideally you want your business to grow and that means more and more data.

You design should consider that possibility. Assuming your database is hosted on a VM, it should have access to Ram, Processor and Storage so you can Scale the system up when ever required.

Same goes for High Availability and Disaster Recovery. Project requirements change and new requirements get added. A smart DBA should keep those in mind before-hand and not be caught off guard. Plan ahead. Keep the possibility of inter-VLAN connection open. Propose the features like Replication, High Availability Groups from the start.



 

 

Auto-Growth and Auto-Shrink 

It's another important aspect to be considered.

When this decision is left with Windows Admins, their first preference is to save disk. So, they always want to enable both these setting.

Auto-Growth = The database starts with a bare minimum little size. As and when required, the database size increases as more data comes into it.

Auto-Shrink = The database is periodically shrink-ed automatically.


 Both these configs adversely affect the SQL Server performance.

More on this later.

Good Luck on your journey.

Comments

Post a Comment

Popular posts from this blog

Index Clean-Up Scripts

By -
dropping un-used ones, adding missing ones, and fine-tuning the ones I already have. I thought I’d share some of the scripts I’ve been using to accomplish this. Un-Used Indexes Script Declare @dbid int     , @dbName varchar(100);   Select @dbid = DB_ID()     , @dbName = DB_Name();   With partitionCTE (object_id, index_id, row_count, partition_count)  As (     Select [object_id]         , index_id         , Sum([rows]) As 'row_count'         , Count(partition_id) As 'partition_count'     From sys.partitions     Group By [object_id]         , index_id )    Select Object_Name(i.[object_id]) as objectName         , i.name         , Case              When i.is_unique = 1          ...
Read more

forgot sa password and no logins are added

By -
Image
Stop the SQL services Edit the properties of the SQL Service Change the startup parameters of the SQL service by adding a  –m;  in front of the existing parameters Start the SQL services. These are now running in Single User Mode. Start CMD on tthe SQL server Start the SQLCMD command. Now we create a new user. Enter following commands CREATE LOGIN recovery WITH PASSWORD = ‘TopSecret 1′ (Remember SQL server has default strong password policy Go Now this user is created Now we grant the user a SYSADMIN roles using the same SQLCMD window. sp_addsrvrolemember ‘recovery’, ‘sysadmin’ go
Read more

The SQL Server DBA’s Guide to Teradata

By -
Being a long-time devotee of all things Microsoft SQL Server, I had quite a bit of learning to do to get up to speed on our new Teradata appliance. This guide attempts to distill some of what I have learned. I will primarily focus on what I have found most lacking: examples of how to convert SQL Server T-SQL to Teradata SQL. This guide will use the vendor-supplied sample databases:  SQL Server’s AdventureWorksDW2012 , and the  Teradata’s Express 14.0 Retail database . Also, while this is probably self explanatory, the “mufford” object referenced in the Teradata examples is simply my own personal sandbox. You’ll need to replace any “mufford” reference to whatever your development sandbox may be named. Release History: 2012-08-17 – Added UPDATE examples; reformatted 2012-08-12 – Added date examples 2012-08-08 – Initial Release SELECT Statements Simple SELECT SQL Server: Best practice is to qualify the table schema; qualifying the database is optional unless ...
Read more