Tag Info

New answers tagged

6

Is the TCP port SQL Server is listening on open globally? If so, yes I'd be concerned. If there is a password that can be brute-forced or guessed, or an exploit that allows someone to bypass authentication, eventually your database could be compromised. You'll also be vulnerable to attacks that don't require access, such as someone filling up the drive that ...


1

The action described in the question should not be a problem. I was able to create a Post Deployment script and add the following code: USE [tempdb]; GO PRINT DB_NAME(); IF (USER_ID(N'g') IS NULL) BEGIN PRINT 'Creating user [g]...'; CREATE USER [g] WITHOUT LOGIN; END; ELSE BEGIN PRINT 'Dropping user [g]...'; DROP USER [g]; END; It builds ...


2

I think this is what you need. select s.job_id ,s.name as [job_name] ,js.step_id ,js.step_name ,js.subsystem ,js.proxy_id ,js.command , c.credential_identity from sysjobs S INNER JOIN sysjobsteps JS ON S.job_id = js.job_id INNER JOIN sysproxies p ON js.proxy_id = p.proxy_id INNER JOIN sys.credentials as c on ...


2

The group or login that is member of the sysadmin role is indepentent of who owns the database. The login that is mapped to the dbo of the database is basically the owner. You can change this via SSMS or with the query below: ALTER AUTHORIZATION ON DATABASE::[ReportServer] TO [sa]; ALTER AUTHORIZATION ON DATABASE::[ReportServerTempDB] TO [sa]; You can ...



Top 50 recent answers are included