Problems with Big Data
Today Steve Jones notes that Big Data isn't a panacea. It's not going to just solve all problems.
Today Steve Jones notes that Big Data isn't a panacea. It's not going to just solve all problems.
If you have been in the information technology industry long enough, you have probably heard the expression "this adds overhead" when discussing any extra processing added on to what is considered normal processing. Dallas Snider answers the question of additional overhead caused by encryption.
Sometimes we need to break down a complex problem into a multiple stage solution to achieve optimal performance
The Connect system from Microsoft doesn't work that well, but that doesn't mean we shouldn't continue to press Microsoft for change.
The first thing you need to understand about SQL Server is indexes, but somehow many of the basic questions don't often get asked or answered much on forums. Rob Sheldon answers some of these questions about SQL Server Indexes and indexing.
SQL Saturday is coming to Huntington Beach, CA on April 26 2014. This is a free day of training and networking for SQL Server Professionals - there are also 2 paid-for precons on April 25 presented by Jason Horner and Bradley Bell. Register for SQL Saturday Orange County while space is available.
Disk performance can make a difference to your SQL Server instance. Steve Jones discusses a few things this week.
Load tests give the database administrator quite a lot of valuable information and may make the difference between poor and acceptable application performance. But are there any gotchas or traps associated with big data?
Preparing for your first (or next) interview or job in SQL Server. A good introduction from Craig Farrell.
The way that various departments might view a team of technology employees can affect how we interact. Andy Warren remembers a few situations and notes it's always more fun to join a team with a good reputation.
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