SQLServerCentral Best Practices Clinic: Part 3
Part 3 of the analysis of the SQLServerCentral database cluster by MVP Brad McGehee. Follow along as he talks about some SQL Server settings and gives reasons why they should or should not be changed.
Part 3 of the analysis of the SQLServerCentral database cluster by MVP Brad McGehee. Follow along as he talks about some SQL Server settings and gives reasons why they should or should not be changed.
On many SQL Servers database file size, either data or log, may be restricted to a maximum size to ensure there is adequate space on the server. The problem with this is that if your data or log file runs out of space you will get an error message
How important is it that your server record all changes to every row? Probably very important and that is one of the foundations on which RDBMS platforms are built. Steve Jones talks about this being a difference with some NoSQL systems, and why it might not be acceptable to most businesses.
A look back at SQLskills Immersion training from Eric Stefani, who attended the week long class recently. SQLskills provides some amazing training, and is worth attending if want to become better skilled at being a DBA.
This article introduces SQL Server Resource Governor and provides a detailed walkthrough of using Resource Governor to manage the resource utilization of SQL Server.
How can you find a SQL Server job? Craig Farrell brings us an article that shows how you can look for a job and get an interview whether you have very little, or years of experience.
Phil Factor speculates on the damage caused to Cloud providers by the Amazon and Sony Outages.
Storage costs are constantly rising, especially for databases as we gather more and more data. However not all of our data is necessarily the same priority or requires the same hardware. Steve Jones talks about the benefits you might get if you can tier your storage.
I support thousands of databases and I'm running across situations where I have a database that has a data file of a couple hundred megabytes and the associated log file is gigabytes in size! I understand this is because I may not have my transaction log backups scheduled properly. What I'm interested in is an easy way to identify these situations where the SQL log file is too large, so I can go in and further analyze these problem databases without needing to look at each database.
Learn how SQLCLR can be used to replace BCP and xp_cmdshell to export data to comma separated and tab delimited flat files.
It is Friday, the queries are running, and nobody is watching the bill. That...
By Steve Jones
Annabel retired from Redgate Software this week. Across most of my career at Redgate,...
By Tim Radney
As a SQL Server DBA with years of experience tuning production environments, I’ve seen...
Comments posted to this topic are about the item What is the Cloud?
Comments posted to this topic are about the item Changing the Schema
Comments posted to this topic are about the item Index Fragmentation Explained: Page Splits,...
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