New answers tagged

5

I'll weigh in from the user perspective. I have worked extensively (15 or so projects) with one of the automation tools on a SQL Server backend, and results were mixed. Did the DWA tool greatly reduce the time to get a data warehouse up and running, or did the time it took to ramp up on learning the tool eat the time that otherwise would have been gained? ...


2

Eckerson's list is poorly researched. There is a more comprehensive catalogue of data warehouse automation tools on our web site, at http://ajilius.com/competitors. I'll answer your questions from a vendor perspective. Our customers report significant savings in project time. Most DWA products are written by data warehouse people who first want to save ...


0

We are using Linked server to connect to Oracle through OLE DB. the using openquery command to pull data down to SQL server. This will help


0

I feel your pain. I've worked with both SQL Server and DB2. I will admit that IMHO, the data extraction and importing tools are not as simple or straightforward to use in SQL Server as they are in DB2. If you wish to stick to the database tools, here is what I recommend: Create queries to extract your data. Use CONCAT to encase each field with a character ...


2

Starting at the beginning: SQL Server uses statistics objects to generate cardinality estimates for the result set steps during the optimization phase. Cardinality estimates are used to generate a query plan, which is the logical plan by which SQL Server will physically access and retrieve the data in order to satisfy the request. Generally speaking, more ...


0

If you have AUTO_UPDATE_STATISTICS on, then yes, your statistics should update once 20% of the data has been modified. But, if you know it's this process that's throwing your statistics out of whack, you can also update them yourself after the process has run. https://msdn.microsoft.com/en-us/library/ms187348.aspx Call UPDATE STATISTICS on the affected ...


4

Assuming that your assumption is correct regarding the VARCHAR(50) field using a collation of SQL_Latin1_General_CP1_CI_AS, then you should consider altering those alphanumeric "code" fields in each of the tables where it exists, to have a collation of Latin1_General_BIN2. Since the value is derived from an algorithm, the casing of any alpha characters ...



Top 50 recent answers are included