Service-Component Architectures
Service-Component Architectures (SCA) provide a programming model for implementing Service-Oriented Architectures (SOA)
Service-Component Architectures (SCA) provide a programming model for implementing Service-Oriented Architectures (SOA)
Reporting Services is a very handy way to get your SQL Server 2005 data out to end users quickly. It is included with your license and provides a great development environment for reports. New author Adriaan Davel brings us a quick technique for ensuring that multi-select parameters are handled correctly.
If you are forced to nod wisely and keep silent when Reporting Services is mentioned, now is the time to turn ignorance into wisdom, with the help of yet another Simple Talk Cribsheet!
This white paper describes how to set up a load-balanced scalable querying environment for Microsoft SQL Server 2005 Analysis Services so that you can handle a large number of concurrent queries to your Analysis Services servers.
SQL Server memory is primarily used to store data (buffer) and query plans (procedure cache). In this article I'll show how much memory is allocated to the procedure cache (RAM). I'll explain how to determine what plans are in the cache and how often they're used.
One of the techniques that you can use for increasing performance, especially in large SQL Server tables, is partitioning. Andy Warren brings us an overview of what this is and how you can use it in your SQL Server 2005 applications.
LINQ may be getting the most attention in the forthcoming .NET 3.5, but there are also several new language features that add functionality and make life easier for the programmer.
This article discusses: How SQL injection attacks work, Testing for vulnerabilities, Validating user input, Using .NET features to prevent attacks, Importance of handling exceptions
Summarizing data in a SELECT statement using a GROUP BY clause is a very common area of difficulty for beginning SQL programmers. In Part I of this two part series, we'll use a simple schema and a typical report request to cover the effect of JOINS on grouping and aggregate calculations, and how to use COUNT(Distinct) to overcome this.
By HeyMo0sh
As someone who works in DevOps, I’m always focused on creating systems that are...
By Brian Kelley
I am guilty as charged. The quote was in reference to how people argue...
By Steve Jones
Learn how to tie a bowline knot. Practice in the dark. With one hand....
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