Why Are There So Many Editions?
SQL Server has grown from two editions in the v6.5 days to 7 with SQL Server 2008. Why are there so many editions? Steve Jones gives his thoughts.
SQL Server has grown from two editions in the v6.5 days to 7 with SQL Server 2008. Why are there so many editions? Steve Jones gives his thoughts.
This past weekend we were moving database files around because we added new LUNs to an existing production cluster. We went at the old tried and true way, we detached the databases, moved the files, and re-attached the databases. That seemed to work well...
I have been hearing about Microsoft's scripting language called Windows PowerShell which is extensively used nowdays for administering and managing Windows servers and workstations. Exchange Server 2007 and Windows Server 2008 are just two of the Microsoft server products that have included this as part of their administrative tools. I want to know how Windows PowerShell can help me as a SQL Server DBA.
With the full-text search features in SQL Server, along with several hybrid search methods for comprehensive table scanning, companies can better meet specific business needs.
I have always been of the personal opinion that all SQL Server tables have a clustered index. As part of the research I am doing on a new book on High Performance Index Maintenance , and on heaps specifically, I ran across this SQL Server Best Practices...
This SQL School video explains how to use the Data Mining add-in for Excel 2007. The installation and configuration are covered.
New author Jason Crider brings us a few tricks and tips that can help you be a more efficient DBA, or a more efficient employee in general using technology.
These days more and more systems gather data all the time, but are we using that data? Steve Jones comments on the glut of information and some of the problems that creates.
Join SQL Server authors and MVPs for a week of warehousing and get the latest on Microsoft Business Intelligence inside your environment. If you are in any stage of a data warehouse design, administration or planning you won't want to miss out on this free "week of warehousing" webinar series, free from SQLServerCentral.com and in partership with Wrox and Pragmatic Works.
One thing most DBAs try to avoid whenever possible is unexpected downtime. It still happens, and we have to deal with it. This Friday Steve Jones asks in the poll how much it happens to you.
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