IT Answers » SQL Server data warehousing/business intelligence

SSRS Report switch for Operational DB to DWH

An279505 — Wed, 16 Feb 2011 14:43:45 +0000

We currently are running a large report off of the operational DB but in turn used this report to create a DWH in order to get this report to run faster. Before we used a stored procedure with many smaller queries that summed our numbers. Since we have the DWH that stores all this needed data in one or two fact tables (the operational DB is highly normalized) is it better in terms of performance to create one sql statement that pulls these flags on each row (i.e. Gender – F, M, NULL) and then do a sum on the report side by using group by’s or is it a better idea to sum all the numbers in the SQL statement and just throw these summed amounts into individual text boxes?

This is the first Data Warehouse I have ever created or even seen and I am just trying to figure out the capability of this with the use of SSRS. If you need any more specifics or have further questions I can give further detail. Thanks so much!

Sage Mas 500 setting up Microsoft Project link.

Karl Gechlik — Thu, 10 Jul 2008 14:03:13 +0000

I am running Sage M500 – I need to be able to link my project files to my M500/SQL data and vice versa. I see lots of information on functionality but only consultants that want to set it up!

HELP Me do this for free and save the day!

When designing a data warehouse in SQL Server what is the best setting for the varchar data type?

SQL Server Ask the Experts — Tue, 08 Apr 2008 23:14:30 +0000

I am designing a data warehouse database to be implemented in SQL Server. There are a number of variable length character fields for which I intend to use the varchar field type. On previous data warehouse implementations in Oracle, I frequently set the length for the varchar fields higher than the current data length. I did this so that if the source changes to a longer field in the future, it will not be necessary to update the database. Is there any reason not to do this for a SQL Server database? One example would be, if the actual data field is now up to 10 characters, but I want to make the field type varchar (25) in case the source changes to a larger field in the future. Will this have any negative performance implications?

Which is more advanced in an Excel/Microsoft SQL Server Analysis Services environment, MDX or UDM?

SQL Server Ask the Experts — Tue, 08 Apr 2008 22:38:44 +0000

Which is more advanced in an Excel/Microsoft SQL Server Analysis Services environment, MDX or UDM?