No R2
The next version of SQL Server was announced last week and Steve Jones is pleased with the name.
The next version of SQL Server was announced last week and Steve Jones is pleased with the name.
Read when you search for help on the internet. You might miss a very important part of what you must do.
Microsoft through its various GUIs tries hard to "protect" users from SQL, but Phil Factor argues that we don't need protection from code. We just need a better way to "document" the syntax.
A previous tip, SQL Server DDL Triggers to Track All Database Changes, generated a lot of discussion involving ways to make the provided DDL trigger more useful. Check out this tip to expand your knowledge on DDL Triggers.
We've been working really hard on SQL Source Control, and need your input. We're currently working on suggestions from our user forum and on an updated migrations feature that supports all source control systems and works across branches. We'd love it if you could spare 10 minutes to complete this survey. If you complete the survey by Friday June 14, you could win a $100 Amazon voucher. There are two up for grabs!
Describes a design pattern for using CDC to power fast and efficient incremental data loads.
When a disaster occurs, the response from your organization isn't always pre-determined. There are times when you might not want to failover to secondary systems, especially if you don't expect the disaster to last long. How do you decide when to fail over?
Microsoft has introduced a new BI product that will help simplify the data discovery phase for Excel users. “Data Explorer” is an Excel add-in that enhances the self-service Business Intelligence experience in Excel by simplifying data discovery and access. Data Explorer is a preview product so these features may appear differently in the final release.
This metric reports the number of connections that are currently blocked, divided by the total count of current connections.
Most well-balanced SQL Servers will have some degree of blocking. This metric attempts to measure the impact of lead blocking queries against other queries. Higher values indicate that many connections are being blocked, and queries should be tuned to reduce the amount of contention.
Moving data around can be a challenge as the sizes of our databases grow. Steve Jones talks about some of the challenges and some creative ways you might consider moving data.
With Fabric Mirroring, Microsoft is promoting a nice and appealing story for operational reporting...
If you’ve been watching AI roll through the data community and thinking, “this seems...
By Arun Sirpal
Not every production incident is a database in RECOVERY_PENDING or a corrupted event (like...
Comments posted to this topic are about the item SQL Art, Part 4: Happy...
WhatsApp:0817-866-887 Jl. Ahmad Yani No.31, Pattunuang, Kec. Wajo, Kota Makassar, Sulawesi Selatan 90174 (@bcakcumakassar)
Hi All I am trying to find 'bad' characters that users might type in....
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