sql - Union to already massive table vs. create new table -


I have a table that I use to create reports using powerpivot in Excel. The table has 30 columns and ~ 2m lines, and due to this huge # column and rows, the excel file is already ~ 20 MB (and yes, I use every single column in that table).

The business has asked Excel to add a new data, which will add three new columns and ~ 1M lines. I am worried about what will happen to affect my excellence and size. Unfortunately I can not join because the current table has a different hierarchy level

I was thinking of modifying the stored procedures of the current table in that table, to improve the table, the new table Rather than dragging, join the new Powerpivot data model.

What is the "better" approach here? Can a union be included within SQL or a union within SQL? Do <- do not feed Excel with large scale union-style tables to do a pivot questions.

Already being invented for the same purpose. Excel may connect to this kind of data source for a while.

The name changed several times to make the cube using Microsoft's SQL Server and other DB providers also received similar support.

The basic concept is the same. Pump your data into a skilled generalized cross-indexed structure. Use excel and other tools to analyze that structure.

The flaw is that you will not be able to see "online" data and in case of Microsoft SQL, it will be necessary to purchase special licenses to be able to use it. / P>

Comments

Popular posts from this blog

Verilog Error: output or inout port "Q" must be connected to a structural net expression -

jasper reports - How to center align barcode using jasperreports and barcode4j -

c# - ASP.NET MVC - Attaching an entity of type 'MODELNAME' failed because another entity of the same type already has the same primary key value -