database features

Question

database features

Viewing 7 posts - 16 through 21 (of 21 total)

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

Eric M Russell SSC Guru Points: 125565 More actions · Answer 1

You probably don't want your development environment to have features that are not expected to be deployed in production, unless the feature is being used to facilitate the development process. For example, the developers may want to use SSIS to refresh the development database from production or they may use SSRS to run data analysis reports, even though SSIS / SSRS won't be used in production.

"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho

starttreck2016 Ten Centuries Points: 1215 More actions · Answer 2

in general , do most of dbas always install ssas and ssis and ssrs when installing sql server 2014

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

sqlserverDBA2016 (10/25/2016)
in general , do most of dbas always install ssas and ssis and ssrs when installing sql server 2014

I can't speak for others but I install everything, no matter which environment, and then disable services that I'm not using so that I don't have to bother with the "WE MUST HAVE <<insert feature name here>> INSTALLED RIGHT AWAY!". It also makes automated installs easy and homogenous except for which features to turn off, which is also easy.

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

Eric M Russell SSC Guru Points: 125565 More actions · Answer 4

Where I've worked in the past, SSIS/SSAS/SSRS is typically installed on a separate box or VM, and sometimes each component warrants it's own dedicated instance. You for sure don't want anything with it's own buffer cache and ad-hoc query engine to be competing for local resources on a high volume OLTP instance.

So, be careful and "don't let the camel get it's nose under the tent". It's OK to run the full SSIS/SSAS/SSRS stack on a single Dev or QA instance for economic reasons, but make it clear that this will never be the configuration in production.

"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho

Ed Wagner SSC Guru Points: 287026 More actions · Answer 5

Eric M Russell (10/26/2016)
Where I've worked in the past, SSIS/SSAS/SSRS is typically installed on a separate box or VM, and sometimes each component warrants it's own dedicated instance. You for sure don't want anything with it's own buffer cache and ad-hoc query engine to be competing for local resources on a high volume OLTP instance.
So, be careful and "don't let the camel get it's nose under the tent". It's OK to run the full SSIS/SSAS/SSRS stack on a single Dev or QA instance for economic reasons, but make it clear that this will never be the configuration in production.

Separate servers for each component? Clearly, you have more server budget than I do. 😉

Tally Tables - Performance Personified
String Splitting with True Performance
Best practices on how to ask questions

Eric M Russell SSC Guru Points: 125565 More actions · Answer 6

Ed Wagner (10/26/2016)
Eric M Russell (10/26/2016)
Where I've worked in the past, SSIS/SSAS/SSRS is typically installed on a separate box or VM, and sometimes each component warrants it's own dedicated instance. You for sure don't want anything with it's own buffer cache and ad-hoc query engine to be competing for local resources on a high volume OLTP instance.
So, be careful and "don't let the camel get it's nose under the tent". It's OK to run the full SSIS/SSAS/SSRS stack on a single Dev or QA instance for economic reasons, but make it clear that this will never be the configuration in production.
Separate servers for each component? Clearly, you have more server budget than I do. 😉

The majority of them are VMs, but yes there is a an Enterprise ETL server that has about 200+ SSIS packages scheduled. Over the past year we've been consolidating ETL processes onto this instance to remove the load from line of business databases. There is another Enterprise Data Warehouse server running those packages that load the data warehouse, and at least one dedicated SSAS server containing some massive cubes. They support a national retailer with 2000+ store locations and an eCommerce website.

However, I can certainly picture a departmental database server, something like HR or billing running the full MSSQL/SSIS/SSAS/SSRS stack on their own instance.

"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho

Jeff Moden SSC Guru Points: 1004439 More actions · Answer 7

sqlserverDBA2016 (10/25/2016)
in general , do most of dbas always install ssas and ssis and ssrs when installing sql server 2014

Dunno. I've never been one to follow the proverbial crowd. I've only explained what has worked very well for me, especially when someone walks into my cube and claims "We need this NOW!". It doesn't take much extra space on today's hard-disks and is oh-so-convenient when the eventuality occurs. If it turns out they didn't really need it, it takes about the same amount of time to turn it off as it did to turn it on... seconds.

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