Frequently an organization will find that the same resources are used in multiple ETL applications, for example, the same database, general purpose processing logic, or file system locations. Creating an easy way to reuse these resources across multiple applications would increase efficiency and reduce errors. Moreover, not every ETL developer has the same skill set, and it is likely that one developer will be more adept at writing code while another is more comfortable configuring database connections. Real productivity gains will come when these developers are able to work independently while still making their work available to others assigned to the same project. These are the benefits of a centralized version control system.
SQLAuthority News – Fast Track Data Warehouse 3.0 Reference Guide
https://docs.microsoft.com/en-us/previous-versions/sql/sql-server-2008-r2/gg605238(v=msdn.10)?redirectedfrom=MSDN I am very excited that Fast Track Data Warehouse 3.0 reference guide has been announced. As a consultant, I have always enjoyed working with Fast Track Data Warehouse project as it truly expresses the potential of the SQL Server Engine. Here are a few details of the enhancement of the Fast Track Data Warehouse 3.0 reference architecture.
SQL SERVER – Summary of Month – Wait Stats and Wait Type – Day 28 of 28
I am glad to announce that the month of Wait Types, Wait Stats and Queues is very successful. I am glad that it was very well received and there was a great amount of participation from the community.
SQL SERVER – WRITELOG – Wait Type – Day 17 of 28
WRITELOG is one of the most interesting wait types. So far we have seen a lot of different wait types, but this log type is associated with log file which makes it interesting to deal with.
SQL SERVER – LCK_M_XXX – Wait Type – Day 15 of 28
SQL SERVER – Reducing Page Contention on TempDB
I have recently received following email asking about how to reduce page contention on TempDB.
“We are using Trace Flag 1118 to reduce the tempDB contention on our servers (2000 and 2005). What is your opinion?
We have read lots of material, would you please answer me in single line.”
SQL SERVER – Shrinking Database is Bad – Increases Fragmentation – Reduces Performance
Earlier, I had written two articles related to Shrinking Database. I wrote about why Shrinking Database is not good.





