n a database I currently support, the application makes use of db_datareader and db_datawriter to give permissions to the tables. In a different database, it's even worse as the application uses db_owner. We're adding new tables to both databases and we don't want the application to have access to these tables. How can I deal with the use of these three roles?
A new idea from a small startup may revolutionize the way that you search for data.
Before adopting NoSQL for a commercial application that needs consistency and durability, you need to be satisfied that the product actually provides all those niceties that the user of relational database systems take for granted.
Resource Governor provides a great mechanism for throttling resources, but it doesn't always allow granular control. Read about this trace flag that allows you to dynamically alter the resource usage of a query.
If you’re involved in the database world it’s hard to have missed the rise of the “no-sql” database products, designed to – depending on your view or the product I suppose – make databases simpler, break out of the transaction database paradigm, scale out across hundreds of machines, make it easy to change the db design (or not require one). I think some of the problems no-sql tries to solve are real, others reflect a lack of awareness/training/tools on how and why relational databases could not just solve the problem, but solve it better.
Pivoting SQL Server tables is always awkward, even with the PIVOT and UNPIVOT operators. If you want to get the job done without GROUP BY or PIVOT, here is a way to do it using only REPLACE.
Join us on April 6th in Omaha for SQL Saturday #197. SQLSaturday is a training event for SQL Server professionals and those wanting to learn about SQL Server.
This Friday Steve Jones talks about xp_cmdshell and the security regarding its use. Do you have any holes that might exist if administrators are allowed to use this tool on their instances?
In this tip we will look at one way to achieve control of stored procedures to ensure that reuse is for the intended purpose and changes do not break other applications that may be using this same code.
A case study shows how the combination of Azure and Hadoop helped the Halo 4 team grow their successful franchise.
By Steve Jones
It’s Prime Day. A few of my recommendations, since I want to do some...
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...
Comments posted to this topic are about the item SQL Art, Part 4: Happy...
Comments posted to this topic are about the item Concurrency and Baseline Control: Level...
Comments posted to this topic are about the item Spending Time in the Office
I have this code on SQL Server 2022. What happens when it runs all at once?
DROP TABLE IF EXISTS dbo.Commission GO CREATE TABLE dbo.Commission (id INT NOT NULL IDENTITY(1,1) CONSTRAINT CommissionPK PRIMARY KEY , salesperson VARCHAR(20) , commission VARCHAR(20) ) GO INSERT dbo.Commission ( salesperson, commission) VALUES ( 'Brian', 12 ), ( 'Brian', 'None' ) GOSee possible answers