Gail Shaw's SQL Server Howlers
For the latest in our series of SQL Server Howlers, we asked Gail Shaw which common SQL Server mistakes and misunderstandings lead to tearful DBAs and plaintive cries for help on the forums.
2012-09-10
3,694 reads
For the latest in our series of SQL Server Howlers, we asked Gail Shaw which common SQL Server mistakes and misunderstandings lead to tearful DBAs and plaintive cries for help on the forums.
2012-09-10
3,694 reads
To kick off a series of DBA worst case scenarios, we asked Phil Factor to confess. He came up with a classic: The mistaken belief that a backup WITH CHECKSUM guaranteed a good backup that could be restored, and the ensuing disaster.
2012-02-02
5,280 reads
By Kevin3NF
Parts 1, 2 and 3 got you to the (SQL) engine room. Now we...
By gbargsley
Whether you’re a seasoned DBA or just exploring database tools, DBeaver offers a powerful,...
DBAs should never run SSMS under their everyday Windows account If you open SSMS under...
Immediate need for a hands-on SQL Server DBA. This is a greenfield opportunity to...
Import-Module ImportExcel # Path to your .sql file $sqlFile = "C:\Data\MyQueries.sql" $excelPath = "C:\Data\SqlExtract_$(Get-Date...
I have noticed sp_executesql also makes a single plan for a stmt with parameter...
If I want to track which login called a stored procedure and use the value in an audit, what function can I use to replace the xxx below?
create procedure AddNewCustomer @customername varchar(200) AS BEGIN DECLARE @added VARCHAR(100) SELECT @added = xxx IF @customername IS NOT NULL INSERT dbo.Customer ( CustomerName, AddedBy ) VALUES (@customername, @added) ENDSee possible answers