new 2014 implementation

Question

new 2014 implementation

mfriessnig

Old Hand

Points: 354
More actions
November 13, 2014 at 7:09 pm

#295099

we are impementating sql server 2014 for data warehousing. is this version stable?
we are going to start out with a 600gig hard drive. can anyone recommend a drive?
our source system has less than a terabyte and we will only bring some of it over.
We are going to have 2 pyhscial processors that are dual core with 8 gig of memory.
Does this config sound good?

Viewing 8 posts - 1 through 7 (of 7 total)

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

happycat59 One Orange Chip Points: 29389 More actions · Answer 1

mfriessnig (11/13/2014)
we are impementating sql server 2014 for data warehousing. is this version stable?
we are going to start out with a 600gig hard drive. can anyone recommend a drive?
our source system has less than a terabyte and we will only bring some of it over.
We are going to have 2 pyhscial processors that are dual core with 8 gig of memory.
Does this config sound good?

Without knowing anything about proposed usage of this data, the only question I can answer is whether SQL 2014 is stable - the answer to that question is definitely Yes.

As for the rest of your questions, they all depend on usage. If you have very few users who don't ask much - this config may well be OK for you. If you have a lot of users, it will be no where near sufficient.

mfriessnig Old Hand Points: 354 More actions · Answer 2

thanks! yes we will have a very low number of users. many reports will run off hours. We need it to merge data and

aggregate.

Any ideas on the disk drive?

Grant Fritchey SSC Guru Points: 398886 More actions · Answer 3

If you have the money, you'd better off with more than one disk to stripe the access. Also, for ~600gb of data, 8gb is a shockingly small amount of memory. I'd recommend at least 32gb to support that much.

"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

Summer90 SSC-Dedicated Points: 32891 More actions · Answer 4

At bare minimum after you install SQL2014 install the MS14-044 security patch KB2977215

This link may help you.

[/url]

Jeff Moden SSC Guru Points: 1004356 More actions · Answer 5

Always shoot big on memory. As has already been stated, 8GB is shockingly low for a 600GB DB. You can't just think user, connections, and queries... you also have to think backup buffers, index maintenance, stats maintenance, integrity checks, and special purpose queries such as a detailed call to sys.dm_db_index_physical_stats, etc, etc.

Don't go cheap on disks, either. I recommend doing a bit of an analysis and make sure that you have enough disk for at least 2 years of growth online and pre-allocated and, I agree... the logical drives should be striped for performance and reliability. Don't forget that backup disk space should be about 3 times the size of the used portion of the database.

As a play on words to "Red" Adair's famous quote, if people think it's expensive to buy the right stuff, wait until you buy the wrong stuff. 😉

--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)

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 6

mfriessnig (11/13/2014)
We are going to have 2 pyhscial processors that are dual core with 8 gig of memory.
Does this config sound good?

I think my cell phone has more than 8GB of memory...

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Summer90 SSC-Dedicated Points: 32891 More actions · Answer 7

My advice to you would be don't skimp on memory. It is cheap and it is the best thing you can do to get good performance out of SQL Server. The more the memory the better. Buy as much as you can get into that server. By the time you have Windows and all of the other minor software on that server it has sucked up 2 gig easily... and you don't want to strangle the operating system from memory when it wants it.