Picking Service Accounts
It is something you do rarely, but with SQL Server 2005 and ten services, there are more decisions to make. Steve Jones gives some advice on which service accounts to choose and some common problems with others.
It is something you do rarely, but with SQL Server 2005 and ten services, there are more decisions to make. Steve Jones gives some advice on which service accounts to choose and some common problems with others.
Most of the time, it's the simplest tools that have the biggest impact on our lives. If you have a camera and believe, like Leonardo DaVinci, that simplicity is the ultimate sophistication, then why not enter Red Gate's Ingeniously Simple Tools photo competition...
To enter is simple. All you need to do is send us a photo of your favorite, simple tool.
One of our expert authors has written some encryption tools for the community to use. However as he readies an extensive series, he's looking for some testers that want to work with encryption on the SQL Server 2000 servers.
There are many changes in SQL Server 2005, especially for the SQL Server developer. New options, features, and changes in the way you program. New author M. Choirul Amri brings us the first in a series on the changes from the point of the developer.
Doug Reilly gives his personal perspective on the responsibilities of a cancer-surviving software developer.
One of our community is working on a thesis for his graduate degree on the effects of outsourcing on knowledge transfer among software engineers. He's got an anonymous survey setup, so if you have a few minutes, lend a helping hand.
Choosing a backup solution can be a trying exercise with all the various add on products these days. New author David Bird gives us some insight into his testing and decisions with a look at Litespeed and Tivoli's Storage Manager.
SQL Server 2005 has substantially enhanced its ETL capabilities, but many people will still be working with DTS in SQL Server 2000 for many years. New author James Greaves brings us a technique for working with imports and handling files that might not have any data.
Healthcare applications come and go, but data live on forever. We’ve seen that since the beginning of the computer industry; when we move from legacy systems into more “modern” architectures, we often leave behind applications, but we almost always take along the data into the future. Even though data are so important, we in health-IT don’t seem to spend the quality time necessary to structure our schemas and databases in such a way as to make it easier to maintain in the future. We often don’t design our data models solidly, and we don’t test them well by putting them through simulations or design them for multiple versions.
Are you mad? Not angry, more like crazy when it comes to designing databases in SQL Server? Don Peterson has met a few people he thinks are just that when it comes to building lookup tables. Does it stem from poor understanding of database design? Or do you disagree? Read Don's case against this particular design practice.
By gbargsley
Have you ever received the dreaded error from SQL Server that the TempDB log...
By Chris Yates
Artificial intelligence is no longer a distant concept. It is here, embedded in the...
Every Scooby-Doo mystery starts with a haunted house, a strange villain, and a trail...
Comments posted to this topic are about the item The Tightly Linked View
Comments posted to this topic are about the item Build a Test Lab of...
Comments posted to this topic are about the item Remembering Phil Factor
I try to run this code on SQL Server 2022. All the objects exist in the database.
CREATE OR ALTER VIEW OrderShipping AS SELECT cl.CityNameID, cl.CityName, o.OrderID, o.Customer, o.OrderDate, o.CustomerID, o.cityId FROM dbo.CityList AS cl INNER JOIN dbo.[Order] AS o ON o.cityId = cl.CityNameID GO CREATE OR ALTER FUNCTION GetShipCityForOrder ( @OrderID INT ) RETURNS VARCHAR(50) WITH SCHEMABINDING AS BEGIN DECLARE @city VARCHAR(50); SELECT @city = os.CityName FROM dbo.OrderShipping AS os WHERE os.OrderID = @OrderID; RETURN @city; END; goWhat is the result? See possible answers