Re: Design choice in the Use of SQl Server Views for ETL



well... the impact depends on the complexity of your queries.
if your queries do large and complex joins, then the impact can be important on the M server. so going through MCopy is a good idea.

moving data from M to MCOPY or M to ODS (using simple views) should results on the same performance, but the design is simplified.

compare the price of maintaining MCOPY versus adding memory and disks on the M server. adding disks and memory can improve the end user access and your design, so everybody is happy.


"RK" <RK@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:7884C0B1-CE23-441A-8805-D1DFEDA5B7F2@xxxxxxxxxxxxxxxx
Hi Jeje,

Wont the use of views based in the database M cause performance problems.
For instance if I were to use normal data views every time a view is run as a
part of the ETL, its going to run a query on the M database further
constraining performance of the already constrained database M.

Using indexed view directly on database M in that server would mean the
overhead of having to maintain the data in the indexed views by the updates,
inserts and deletes happening in the underlying tables in database M means
again potentially poor response times on the application runnng based on
database M.

Hope you understand my concern.

Thanks

RK

"Jeje" wrote:

your solution M --> MCOPY --> ODS appear to be a good one.
but have you try to do M --> ODS?
maybe you can upgrade the M server to support more queries, this solution
simplify the overall process.

where do you want to use indexed views?
if it's on the MCOPY server, there is no advantage of these indexed views.
but using views as the source of your ETL process is a good option.


.



Relevant Pages

  • Re: Design choice in the Use of SQl Server Views for ETL
    ... maybe you can upgrade the M server to support more queries, this solution simplify the overall process. ... 2000 database. ... Server 2005 server and lets call this database as MCOPY. ... similar structure in the ODS using SSIS packages. ...
    (microsoft.public.sqlserver.datawarehouse)
  • Re: Design choice in the Use of SQl Server Views for ETL
    ... Now coming to moving data from M to ... MCopy will be in a SQl 2005 server, I cant use Log shipping to do this. ... Wont the use of views based in the database M cause performance problems. ...
    (microsoft.public.sqlserver.datawarehouse)
  • SUMMARY: V440 small DATABASE SERVER
    ... apprehensive about how few disks you're using. ... PICK variant database, so your mileage with my "advice" may vary. ... the App is tuned to not do crazy IO (queries tuned), ... We had a small extranet server running a fairly classic "3-tier" client ...
    (SunManagers)
  • Re: Performance Improvements: Hardware vs. DB Design
    ... > I recently designed & developed a data warehouse for a client of ours. ... > database with a substantial amount of data, ... I think many companies are inclined to add more server ... the queries, revise the indexes if necessary, and verify the reporting ...
    (microsoft.public.sqlserver.server)
  • Re: Limiting the number of records returned in DAO recordset
    ... environment queries that are only returning 200 records can be ... unbelievably slow at times (today it varied between 4 and 78 seconds ... I think a server based db should be faster but I also want it so as to ... A database server will not necessarily be "faster" than a local database if ...
    (microsoft.public.vb.database)

Loading