Moving Database Files in SQL Server
A short article that talks about the isues with moving SQL Server database files around on your storage subsystem.
A short article that talks about the isues with moving SQL Server database files around on your storage subsystem.
This week Steve Jones notices some good advice from Brent Ozar and the fastest query in your database.
As databases grow, it often becomes necessary to add new I/O paths to accommodate the growing space. Even without growth that requires this scale, it can still be useful to utilize multiple I/O devices to spread out the load. One way that you can make optimal use of new drives is to add a filegroup to the database and move certain objects (say, all of your indexed views) to the new filegroup.
SQL Saturday comes back to Vancouver, BC on Feb 16, 2013. Come join in if you can.
Steve Jones is up in the Redmond area at Microsoft's HQ looking for SQL Server developers. This editorial was originally published on April 17, 2008. It is being re-published as Steve is on holiday.
Windows Server 2012 introduces native deduplication functionality. While this is a promising new Windows feature for other file types and characteristics, there are some potential pitfalls that you need to be aware of when it comes to deduplication specifically for SQL Server backup files.
Interviewing for a database position is a careful game of give and take. Knowing what to expect and how to prepare for your interview is important, but it's only half the battle. You'll also need to ask questions to see if the job, and the company, is a good fit for you.
In NYC on Feb 21 at 6:30, Don Gabor has a short seminar to help with your networking. Whether you are chatting in small groups or one-on-one at a networking event, IT conference or after-hours party, your ability to master the art of conversation will help you find and connect with business contacts.
IBM is sending a Watson supercomputer to college. We don't know what will happen with this experiment, but it is exciting for those of us looking forward to interacting more with computers in the future.
A brief look at the Varbinary data type and its uses in SQL Server for beginners.
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