New answers tagged

0

If data from the previous day or from the early morning would do, then a BACKUP/RESTORE cycle is your best bet. Basically, you back up the Production DBs, then restore those to the locations that you need the updated data in. Note that doing this to certain environments every day will break your processes. Restoring daily to Dev, for example, will overwrite ...


1

I experienced this issue and it has been resolved by removing the SPN entry in the attributes of the computer account in AD for the server Find the machine account in AD Users and Computers(Advanced view) Then remove the two entries in servicePrincipalName for MSSQLSvc


2

For Jobs, you cannot use syslogins as the owner may be part of a group and not exist in logins. Use the below select msdb.[dbo].[SQLAGENT_SUSER_SNAME](owner_sid), * from msdb.dbo.sysjobs


0

It has been already showed before that before dropping a user you need to reassign any schema it might own to dbo as per the example below: alter authorization on schema::YourSchemaName_Ownedby_TheUserYouWantToDelete to dbo go drop user TheUserYouWantToDelete go However, sometimes the user you want to delete has more than one schema assigned to it. You ...


0

This worked for me. USE msdb GO EXECUTE dbo.sysmail_stop_sp GO


0

I experienced this issue just recently. I was running as the NT SERVICE account and when I switched to using a service account, I could no longer connect using SSMS with the machine name or the FQDN. I could connect with the IP address. With some digging I found that the SPN in Active Directory for the SQL instance was registered on the machine. Once I ...


2

The solution was to change the NLS_LANG value in the registry to "AMERICAN_AMERICA.US7ASCII" because of reasons described in these answers: If we have US7ASCII characterset why does it let us store non-ascii characters? difference between NLS_NCHAR_CHARACTERSET and NLS_CHARACTERSET for Oracle Now the characters are coming through correctly. Thanks @...


Top 50 recent answers are included