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.
It is Friday, the queries are running, and nobody is watching the bill. That...
By Steve Jones
Annabel retired from Redgate Software this week. Across most of my career at Redgate,...
By Tim Radney
As a SQL Server DBA with years of experience tuning production environments, I’ve seen...
Comments posted to this topic are about the item What is the Cloud?
Comments posted to this topic are about the item Changing the Schema
Comments posted to this topic are about the item Index Fragmentation Explained: Page Splits,...
I set up a few users on my SQL Server 2022 instance.
CREATE LOGIN User1 WITH PASSWORD = 'Demo12#1' CREATE USER User1 FOR LOGIN User1 GO CREATE LOGIN User2 WITH PASSWORD = 'Demo12#2' CREATE USER User2 FOR LOGIN User2 GO CREATE LOGIN User3 WITH PASSWORD = 'Demo12#3' CREATE USER User3 FOR LOGIN User3 GOI then created a schema that one of them owned. Under this schema, I added a table with some data.
CREATE SCHEMA MySchema AUTHORIZATION User1
GO
CREATE TABLE Myschema.MyTable(myid INT)
GO
INSERT MySchema.MyTable
(
myid
)
VALUES
(1), (2), (3)
GO
SELECT * FROM MySchema.MyTable
GO
I granted rights and verified that User2 could access this table.
GRANT SELECT ON Myschema.MyTable TO User2 GO SETUSER 'USER2' GO SELECT * FROM MySchema.MyTable GOThis worked. Now, I move this schema to a new user.
ALTER AUTHORIZATION ON SCHEMA::Myschema TO User3; GOWhat happens with this code?
SETUSER 'USER2' GO SELECT * FROM MySchema.MyTable GOSee possible answers