An AlwaysOn Bug with Service Broker Transmission Queue
Paul Brewer talks about an AlwaysOn problem affecting the Service Broker Transmission Queue.
Paul Brewer talks about an AlwaysOn problem affecting the Service Broker Transmission Queue.
Graph database are an intriguing alternative to the relational model. They apply graph theory to record the relationships between entries more naturally, and are a good fit for a range of data tasks that are difficult in SQL. Buck Woody gives an introduction to Graph databases and shows how to get Neo4J up and running to get familiar with the technology.
When you need to find all the related rows and tables to a parent table, here's one way you might approach the problem.
Work on your professional development plan in 2014. Steve Jones has a little advice for you.
You need a SQL Server-based application that will work with huge amounts of data and must perform calculations of startling complexity. How far will you go to deliver the required performance?
You have imported an assembly into a SQL Server database to use the CLR functions and stored procedures it contains. However later, you lost the original .dll file and you would like to create the .dll file again from what's in the database. In this tip, we look at how you can recreate the .dll file.
SQL Saturday is coming to Albuquerque on January 25, 2014. Join us for a free day of SQL Server training and networking. This SQL Saturday also features 2 paid-for preconference sessions presented by Denny Cherry and William E. Pearson III.
Red Gate are looking for participants in a short short survey on SQL Server database releases. At the end you will be given a chance to enter an e-mail address to win a $50 Amazon gift certificate.
Steve Jones requests today that DBAs learn to work with developers and make us all more efficient. He asks for your ideas about how we might go about doing this.
Receive Deadlock info from the SQL Error Log every time a deadlock occurs.
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...
It is Friday, the queries are running, and nobody is watching the bill. That...
Comments posted to this topic are about the item SQL Art, Part 4: Happy...
Hi All I am trying to find 'bad' characters that users might type in....
WhatsApp: 0817839777 Kw. Industri Pulogadung, Jl. Raya Bekasi Km. 21, Ruko No.A2/18-19, RW.3, Wil,...
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