The Weekly Update for Dec 31, 2007
Interviewing, Google as a monopoly, Cumulative Update 5 and more.
2007-12-31
118 reads
Interviewing, Google as a monopoly, Cumulative Update 5 and more.
2007-12-31
118 reads
Get a high-level overview of the benefits of the extensibility framework in SQL Server 2005 Analysis Services that allows independent software developers to easily integrate new data mining algorithms into the product.
2007-12-31
1,647 reads
We've got a new contest running for the next week just for your production DBAs. Win a prize just for telling us a story.
2007-12-28
2,640 reads
If you are a SQL Server DBA, you realize that the performance of cursors is not great and they should be avoided where possible. One place it is difficult to avoid cursors is individual row processing within a trigger. Amin Sobati brings us a new article that shows just how you can avoid this.
2007-12-28 (first published: 2006-12-07)
47,974 reads
In working on an existing database, DBAs often look to normalize tables and correct obvious flaws in design. Recently Andy Warren was working on a consulting project and realized that defaults would prevent many issues.
2007-12-28 (first published: 2007-01-04)
7,192 reads
This white paper covers a variety of client object models supported by Microsoft SQL Server Analysis Services when connecting to relational data sources. The example problems and solutions were gathered by members of the Analysis Services team while working with users of Analysis Services.
2007-12-28
2,119 reads
SQL Server 2005 provides four methods of encryption. Part one of this article covers encryption and decryption by passphrase.
2007-12-28
2,818 reads
Part 3 of his series looking at SQL Server Compact Edition, then embedded version of SQL Server. This time we look at the new version that's in beta.
2007-12-27
2,219 reads
An exploration of the process of translating a conceptual model to a logical model, and ultimately, a faithful implementation using T-SQL.
2007-12-27
3,035 reads
Gregory Larsen discusses how to use the TOP clause to help solve requests where you want to restrict the number of records returned based on a record count.
2007-12-27 (first published: 2007-01-05)
8,395 reads
By Brian Kelley
If your organization is spending money, then meaningful results are a must. Pen testing...
By HeyMo0sh
In my experience, FinOps success has never been just about tools or dashboards. It...
By HeyMo0sh
As a DevOps person, I know that to make FinOps successful, you need more...
Comments posted to this topic are about the item Restoring On Top II
Comments posted to this topic are about the item SQL Art 2: St Patrick’s...
Comments posted to this topic are about the item Breaking Down Your Work
I have a database, DNRTest, that has a number of tables and other objects in it. The other day, I was trying to mock up a test and ran this code on the same server:
-- run yesterday CREATE DATABASE DNRTest2 GO USE DNRTest2 GO CREATE TABLE NewTable (id INT) GOToday, I realize that I need a copy of DNRTest for another mockup, and I run this:
-- run today USE Master BACKUP DATABASE DNRTest TO DISK = 'dnrtest.bak' GO RESTORE DATABASE DNRTest2 FROM DISK = 'dnrtest.bak' WITH REPLACEWhat happens? See possible answers