DBAs: Stop Denying Sysadmin to Developers
Kendra Little explains why DBAs don't allow sysadmin permissions in development, and why, it at all possible, they should.
2019-05-31
Kendra Little explains why DBAs don't allow sysadmin permissions in development, and why, it at all possible, they should.
2019-05-31
SQL Vulnerability Assessment is a feature available in the latest versions of SQL Server Management Studio (SSMS). This feature is very easy to use and it will show you...
2019-05-15
Another post for me that is simple and hopefully serves as an example for people trying to get blogging as #SQLNewBloggers. Which of these is more complex? GRANT SELECT...
The...
2019-05-10
If you have to deal with linked servers then you probably have or will run into the following error: Login ... Continue reading
The post Why am I getting an...
2019-05-08
The sa account is the most powerful account in a SQL Server instance, and most DBAs disable it. There are several other built-in accounts that you may not think about that often. Robert Sheldon continues his SQL Server security series with an article about built-in accounts.
2019-05-08
This doesn’t require much in the way discussion. This isn’t exactly a huge issue since I don’t think granting db_owner ... Continue reading
The post db_owner in msdb == sysadmin...
2019-05-06
Security is often considered the most important of a database administrator's responsibilities. SQL Server has many powerful features for security and protecting data, but planning and effort are required to properly implement them. In this article, the first of a series, Robert Sheldon reviews the many components available to secure and protect SQL Server databases.
2019-01-28
2,859 reads
For many developers, database security and Access control is just something that gets in the way of development work. However, several recent security breaches have had devastating consequences and have caused a change in attitude about the value to any organisation of having database applications that meet industry standards for access control and security. The problem, however is in admitting that you have a problem and finding answers to those problems you are just too shy to ask in public.
2017-01-05
7,712 reads
By Vinay Thakur
I wrote about TempDB Internals and understand that Tempdb plays very important role on...
By Vinay Thakur
continuing from Day 1 where we covered the history of AI and GPT family,...
By Steve Jones
It’s a day off for Redgate today. This is our annual wellbeing day, where...
Comments posted to this topic are about the item A Quick Restore
Comments posted to this topic are about the item Guarding Against SQL Injection at...
I have a quick question on Ola Hallengren Index Optimize Maintenance . Do we...
While doing some testing of an application, I wanted to reset my environment after doing some testing with this code:
USE DNRTest BACKUP DATABASE DNRTest TO DISK = 'dnrtest.bak' GO /* Bunch of stuff tested here */RESTORE DATABASE DNRTest FROM DISK = 'dnrtest.bak' WITH REPLACEWhat happens if this runs, assuming the "bunch of stuff" isn't anything affecting the instance. See possible answers