Come to the Charleston PASS SQL Server User Group
The Charleston, SC PASS chapter is looking for speakers and new members. Read more and come to the Sept 20 meeting if you are near the area.
The Charleston, SC PASS chapter is looking for speakers and new members. Read more and come to the Sept 20 meeting if you are near the area.
Laerte Junior was asked for a quick and easy way to save the output from the Get-EventLog cmdlet in a SQL Server table. Luckily, he already knew about Chad Miller's excellent Out-DataTable and Write-DataTable functions, and has laid out everything we need to use them like pros.
Today we have a guest editorial from Andy Warren. Andy talks about the relationships we have at work with our management and how sometimes the indirect reports are hard to deal with.
We are conducting new product research and are keen to speak to people who have any experience (good or bad!) using Microsoft's SQL or Windows Azure. If you're interested and would like to get involved--tell us your frustrations, shape a new product, test-drive betas etc
It comes as rather a shock to find out that one of the commonest circumstances in an OLTP database, an ascending primary key with most querying on the latest records, can throw the judgement of the Query Optimiser to the extent that perfomance nose-dives. Fabiano Amorim once again dons snorkel and goggles to explore the murky depths of execution plans to find out why.
Moving to the cloud, or any other type of outsourcing should be done with common sense, as Steve discusses today. That means keeping control of your backups.
There are numerous circumstances when we wish to add a custom function to a SSRS report in order to cater for needs of the customer which exceeds the capability of the built-in functions in SSRS. In these scenarios we will have to write our own functions. In this article you will see how to add custom code to SSRS.
On Thursday September 15th, MCM Robert Davis will discuss the architect jobs and their meanings.
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