MSSQL 2014 with 3par

SQL Server Administration
1

Anyone have experience of installing 2014 into a 3 par storage?any hints or guide to design the filegroup?

2

Some general thoughts:

  1. Have separate filegroups for metadata (use the PRIMARY), data, indexes and logs
  2. Put Tempdb and logs on different ports than metadata/data/indexes and each other
  3. consider using Buffer Pool Extensions (new with 2014)

To get more specific, what are you putting on your database? OLTP? OLAP? How big will your tables be? How frequently updated? Have you considered in-memory tables or columnstore tables?

1 Like
3
  1. Have separate filegroups for metadata (use the PRIMARY), data, indexes and logs
    Ans. Not quite sure what you mean but even if we create multiple filegroup in each of the drive, since it was 3par, will it be skew in the physical layer?cause we could not control the data stripping.
  2. Put Tempdb and logs on different ports than metadata/data/indexes and each other
    Ans. in plan.
  3. consider using Buffer Pool Extensions (new with 2014)
    Ans. Will read about it.

To get more specific, what are you putting on your database? OLTP? OLAP?
Ans. OLAP
How big will your tables be? How frequently updated?
Ans. At least 2tb for 5 table.
Have you considered in-memory tables or columnstore tables?
Ans. Yes and that is the main reason for 2014. (of cause with table partition)

4

the purpose of separate file groups is for recoverability as well as performance. see here: placing index

and here:database files

and here: best practices

1 Like