New answers tagged data-warehouse
3
The only 'tool' that can read an MDF and LDF is an appropriately versioned edition of SQL Server. You need to install a SQL Server instance, attach the database to it and then use your preferred ETL tool to connect to this SQL Server and read data from the database.
0
It depends on the purpose of the key. "Surrogate key" can mean different things to different people; to my mind, it means a candidate key (a field or combination of fields which uniquely identify a record) other than the primary key. For example, social security number may be a surrogate key for customers (not a very good one, mind).
If the values are ...
0
A table can and should have as many keys as it needs. Usually when a surrogate key is used it means you will also want some alternative key as well (variously called a domain key, natural key or business key).
The practice of designating any one key as "primary" is of no great significance. It is simply a convention to mark one of the keys as "preferred" or ...
1
You have to use convert DT_WSTR to DT_DBTIMESTAMP. You can find BOL reference here.
for e.g.instead of "Getdate()" use your Date_Column
(DB_TIMESTAMP)((DT_WSTR,4)YEAR(GETDATE()) + RIGHT("0" + (DT_WSTR,2)MONTH(GETDATE()),2) + RIGHT("0" + (DT_WSTR,2)DAY(GETDATE()),2) + (DT_WSTR,10) Time_Column)
Also, you can use the Data Conversion transformation, which ...
4
There are a multitude of factors that go into determining which Teradata platform and the configuration of the platform that will suite your needs. Teradata has spent untold amounts of money on intellectual property and decades of experience working with potential customers to help them properly size a configuration that not only meets the immediate needs of ...
1
Let's tart with the assumption that you only need one fact table for "Orders". This approach is correct in 99% of cases and your scenario is fairly standard.
Declare the gain of the fact table: One row per order line.
Determine the dimensional attributes ( Date ordered, Date shipped, customer, product, etc.) These will be a mixture from both the order ...
2
If you want to de-normalize this into a single fact table, the fact table is going to be about line items. Therefore, the facts from DataSourceAHeader need to be split up and distributed to the relevant line items so they are not duplicated. As it is currently presented, that means dropping your total order cost and calculating this by summing the line item ...
0
Try to get away from arbitrary primary keys. In the case of the orders there is a useful key in the order id. The line numbers are also unique when combined with the order id. Loading the data should trap any exceptions such as duplicates.
All your primary and foreign constraints, for the data you have shared, must be built on order id and line number with ...
Top 50 recent answers are included
