Someone Actually Thought This Through
A response from Great Plains Software on the use of the sa account in Dynamics software.
2001-05-09
4,486 reads
A response from Great Plains Software on the use of the sa account in Dynamics software.
2001-05-09
4,486 reads
Were you aware that the act of populating a temporary table can cause system-wide bottlenecks on your server? Problems can occur both with SQL Server 6.5 and 7.0/2000 in different ways, and in this article Neil Boyle discusses how best to avoid them.
2001-05-08
9,017 reads
A properly configured SQL Server can mean the difference between a sluggish server and one that runs well. There are a few pitfalls that you can experience in doing this.
2001-05-08
3,486 reads
This article by Leon Platt speaks to how you can avoid pulling your hair out when configuring connection pooling for IIS.
2001-05-08
8,182 reads
Using the sa account in development is just plain dumb. Here are some reasons why!
2001-05-08
6,815 reads
The type of datatypes that you use in your schema could impact the performance and the accuracy of your database.
2001-05-07
6,622 reads
Can you run a DTS package from Query Analyzer...you sure can! Read how to integrate DTS, Jobs and Stored Procedures to run a DTS Package from Query Analyzer.
2001-05-07
10,568 reads
In this article, you are shown how to configure StarSQL, which is one method to rapidly connect to DB2 databases.
2001-05-07
3,480 reads
Have you ever worked with an application that forgot to close its connections? Ever run out of connections on your SQL Server and had to manually go remove the ones that are not in use? This article will present a technique for keeping the database clean.
2001-05-07
5,143 reads
So, you've added a linked server and need information about it. There must be an easier way to fine information about your linked server and keep from walking to the server room.
2001-05-07
10,183 reads
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....
Comments posted to this topic are about the item Extreme DAX: Take your Power...
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