Our people who are managing databases (I can't call them DBA's because of the lack of DBA skills) are planning to take backups into the same physical disks as the database data (.mdf) files. Then all these backups are read into a tape. Although they are moving backups into the tape, I think that they should build a new dedicated physical disk for backups. This is because writing backups may cause slowness when reading databases. What do you think?
In SQL Server 2008 there is a permissions VIEW SERVER STATE. What rights this permission give to user? What SQL Server mean by SERVER STATE?
Does the transaction log get truncated when I take a full backup using command
BACKUP DATABASE AdventureWorks
TO Adventurewks
GO
Or do I have to take a log backup separately?
BACKUP LOG AdventureWorks
TO Adventurewks;
GO
Or is the log backup just for a point-in-time restore?
My intention is to be able to send mail from Windows Server 2008. What possibilities do I have? SMTP client, SENDMAIL etc.? What would be the best solution for this?
I'm building SQL Server instance for reporting purposes. My plan is to use AD groups for server and database logins. I have several groups with different roles (admin, developer, user etc.), and I would like to map these roles into SQL Server database roles (db_owner, db_datawriter etc.). What are the pros and cons of using AD groups for logins? What kind of problems you have noticed?