tsql - Why we need to use T-SQL over SQL when creating reports from Data Warehouse? -



tsql - Why we need to use T-SQL over SQL when creating reports from Data Warehouse? -

can tell me why need utilize t-sql on sql when creating reports info warehouse?

sql has functions , joins see of online tutorials utilize t-sql when creating reports dw.

can done sql? if t-sql must, please explain why? in terms of can t-sql sql cannot.

some useful tutorial links t-sql , creating reports great too!

thanks in advance~

regardless fact t-sql has more functionality plain sql, in general info warehousing have 2 main approaches:

put business logic closer data. way develop lots of t-sql functions , apply many optimizations available there improve performance of etl. pros greater performance of etl , reports. cons cost of making changes code , migration cost. usual case growing dwh migration of mpp platforms. if have lots of t-sql code in mssql, you'll have rewrite it, cost pretty much money (sometimes more cost of mpp solution + hardware it) put business logic external etl solution informatica, datastage, pentaho, etc. way in database operate pure sql , complex logic (if needed) responsibility of etl solution. pros simplicity of making changes (just move transformation boxes , alter properties using gui) , simplicity of changing platform. con performance, 2-3x slower in case of in-database implementation.

this why can either find tutorial on t-sql, or tutorial on etl/bi solution. sql general tool (many ansi standards it) , basic skill dwh specialist, ansi sql much simpler not have database-specific stuff

sql tsql data-warehouse

Comments

Popular posts from this blog

Delphi change the assembly code of a running process -

json - Hibernate and Jackson (java.lang.IllegalStateException: Cannot call sendError() after the response has been committed) -

C++ 11 "class" keyword -