A silo is "a deep bin for storing material" as is KIPP Silo. KIPP Silo is the KIPP Network's Self-organized, Iterative, Late-binding (or Lightweight), and Open-source (for now) data warehouse solution.
So, I'll start by saying I'm not the most familiar with SQL Server.
Is it a better option to setup Linked Servers in KIPP Silo, rather than import data into a table and manage from there.
My two concerns against a linked server setup are:
1) Keying. This might be from my general lack of knowledge on the subject, but is keying possible using linked tables? For example, could we setup foreign keys to a studentid field if that field is located in a linked table?
2) I generally like the idea of importing data, since with that case it would be controlled by the data warehouse. In the event of a service changing it's backend or going out of business, we would still have a functioning product.
So, I'll start by saying I'm not the most familiar with SQL Server.
Is it a better option to setup Linked Servers in KIPP Silo, rather than import data into a table and manage from there.
My two concerns against a linked server setup are:
1) Keying. This might be from my general lack of knowledge on the subject, but is keying possible using linked tables? For example, could we setup foreign keys to a studentid field if that field is located in a linked table?
2) I generally like the idea of importing data, since with that case it would be controlled by the data warehouse. In the event of a service changing it's backend or going out of business, we would still have a functioning product.
Thoughts?