Search Results

Sounds to me like a case for a Periodic Snapshot Fact Table, eg Date, TicketsOpened, TicketsClosed, OpenTickets

I have seen this done. And while it's not something I would ever recommend, it does have some advantages from a process and skillset point-of-view. The main reason you would try this is to have a co …

Can someone guide me as to which of these options is the most apt design? Funilly enough, that question does have an answer: No. No one can. Dimensional modeling is always about the questions …

It's quite common in Data Warehouse schema designs to assign a new, integer, single-column key to every table, and retain the source-system key (sometimes called the "business key") as well. Kimbal …

In SQL Server with Table and Index Compression (Row, Page or Columnstore) NVarchar columns don't use two bytes per character. They use Unicode Compression. Here's an example: use master go drop da …

What you describe is basic data warehouse architecture, where you have both normalized transaction data, and from that load tables that are modeled for easy consumption and fast query performance. In …

With that design it is expected that the query requires a full scan of the columnstore. That should be very fast at that scale, but the IO stats show that you're reading from disk. If you look at th …

There are better ways to handle this than dirty reads. READ UNCOMMITTED queries will still block DDL, like TRUNCATE TABLE, DROP TABLE and ALTER TABLE … SWITCH, so it might not even help. First, of c …

As of SQL 2016 Clustered Columnstore Indexes should be your default choice for Fact tables in a Kimball-style dimensional model, possibly with the addition of a non-clustered primary key to prevent du …

The sales_order table contains 7'100'000 rows with size 5.5GB. However, in the data warehouse, the same table sized 20GB SQL Server has several different table compression options. The one most com …

The plans generated for queries with forced recompile are not cached. See RECOMPILE Hints and Execution Plan Caching for details.

You should use an AD account, rather than local Windows accounts which you have to manually keep synchronized among the servers. If the service account is used to run the SQL Server service, it should …

Yes. It is generally safe, and often useful to create indexed views on subscriber tables in transactional replication. You may need to drop and recreate the indexed views using custom scripts before …