In this and the related articles, we will overview Actions in Analysis Services 2005. Much as they did in the previous version of Analysis Services, Actions allow information consumers to go beyond the robust OLAP perspective offered by Analysis Services, and to "step outside" for related information, or to generate commands or initialize programs, without leaving their current analysis focus.
2006-10-24
2,654 reads
Learn how to make life easier by dividing large tables and indexes into smaller parts.
2006-10-23
3,774 reads
It's small and neat but it might just save your data...Robyn Page's crib sheet tells you everything you wanted to know about SQL Server backup but were afraid to ask.
2006-10-20
4,868 reads
Every SQL Server developer has a preferred method of doing things; mine is what I call molecular queries. These are queries assembled from atomic queries; by which, I mean that they address exactly one table. By combing atoms, I can create molecules.
2006-10-19
3,998 reads
The .NET Framework 2.0 and Visual Studio 2005 make it easy to create a basic but extensible database-monitoring solution without a lot of complexity or coding.
2006-10-18
4,043 reads
Sanchan Saxena gets to grips with the new index-tuning tools and features in SQL 2005
2006-10-17
3,510 reads
Are you up to the latest design challenge? A great way to sharpen our analysis and modeling skills is to continuously address real-world scenarios. A modeling scenario with suggested solutions appears each month in this Design Challenge column. The scenario is emailed to more than 1,000 modelers. The responses are then consolidated into this column.
2006-10-16
2,039 reads
This article examines a variety of ways in which you can execute all the SSIS packages in a folder.
2006-10-13
1,958 reads
Arthur Fuller advises DBAs to try to break their software in order to make sure their SQL Server databases can withstand potential attacks. See if your code can hold up to his suggested tests.
2006-10-12
3,499 reads
Database concurrency conflicts are somewhat of a plague in software development because they're hard to predict and handle. Unfortunately, they're also hard to prevent.
2006-10-11
2,638 reads
By Chris Yates
There was a time when the Chief Data Officer lived in the shadows of...
By Rayis Imayev
"But I don’t want to go among mad people," Alice remarked."Oh, you can’t help...
By Steve Jones
I saw some good reviews of the small gemma3 model in a few places...
Comments posted to this topic are about the item Create an HTML Report on...
Comments posted to this topic are about the item We Should Demand Better
Comments posted to this topic are about the item Estimated Rows
I have two calls to the GENERATE_SERIES TVF in this code:
SELECT TOP 10 gs.value FROM GENERATE_SERIES(1, 10) AS gs ORDER BY NEWID () OPTION (RECOMPILE); go DECLARE @a int = 10; SELECT TOP (@a) gs.value FROM GENERATE_SERIES(1, @a) AS gs ORDER BY NEWID () OPTION (RECOMPILE);In the actual query plans, what is the estimated number of rows for each batch? See possible answers