none
regarding ssis - performance tuning

Answers

All replies

  • Sunday, August 25, 2013 6:23 AM
  • Hi,

    How to we load the 10 GB of data with in 30 min?

    Please help me 

    Hello ,

    Simple answer is using SSIS feature by creating simple package.

    http://www.codeproject.com/Articles/173918/How-to-Create-your-First-SQL-Server-Integration-Se

    You can also use Import export wizard.(not available in 2005 express)

    The answer to some extent also depends on hardware and RAM present on your system


    Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

    Sunday, August 25, 2013 6:41 AM
  • Hi,

    if you have large amount of data you have to have powerful CPU ,RAM and using Columnstore index .

    please read the following :

    A columnstore index is stored compressed. The compression factor can be up to 10 times
    the original size of the index. When a query references a single column that is a part of a
    columnstore index, then SQL Server fetches only that column from disk; it doesn’t fetch
    entire rows as with row storage. This also reduces disk I/O and memory cache consumption.
    Columnstore indexes use their own compression algorithm; you cannot use Row or Page
    compression on a columnstore index.
    On the other hand, SQL Server has to return rows. Therefore, rows must be reconstructed
    when you execute a query. This row reconstruction takes some time and uses some CPU and
    memory resources. Very selective queries that touch only a few rows might not benefit from
    columnstore indexes.
    Columnstore indexes accelerate data warehouse queries, not OLTP workloads. Because of
    the row reconstruction issues and other overhead when you update compressed data, tables
    containing a columnstore index become read only. If you want to update a table by using a
    columnstore index, you must first drop the columnstore index. If you use table partitioning,
    you can switch a partition to a different table that does not use a columnstore index, update
    the data there, create a columnstore index on that table (which has a smaller subset of the
    data), and then switch the new table data back to a partition of the original table.
    The columnstore index is divided into units called segments. Segments are stored as large
    objects and consist of multiple pages. Segments are the unit of transfer from disk to memory.
    Each segment has metadata that stores the minimum and maximum value of each column for
    that segment. This enables early segment elimination in the storage engine. SQL Server loads
    only those segments requested by a query into memory.
    You learn more about columnstore indexes and their efficient

    Sunday, August 25, 2013 6:49 AM