![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
I know this is a silly question so I apologize in advance. Is the implementation/ configuration/ design/ loading/ etc. of AS typically the responsibility of a DBA or a Developer of a company? From the perspective where there is a definate difference between the two roles of course. -- SQL2K SP3 TIA, ChrisR |
#3
| |||
| |||
|
#4
| |||
| |||
|
|
Chris Interesting question that I'd never thought about before. I'm a BI developer and control all aspects of the OLAP side. Our DBA dosn't touch AS at all, never had any experience. However, I suppose there is a fair and valid argument that there should be an AS DBA, but should it be the SQL Server DBA.... I'm not convinced, DBA's tend to specialise and excel in OLTP environments and AS is typically NOT OLTP. My view could be swayed by the fact that I do all the AS stuff and have it purring like a kitten. In my view if a SQL DBA is to be involved it should only be in the implamentation and possibly configuration. The design and loading is the simple bit that any of us humble developers can do. |
#5
| |||
| |||
|
#6
| |||
| |||
|
![]() |
| Thread Tools | |
| Display Modes | |
| |