Tag Info

New answers tagged

0

Would it work for you to create a user for the login and assign them a read-only role? <!-- language: lang-sql --> CREATE USER hello FOR LOGIN hello GO EXEC sp_addrolemember 'db_datareader', 'hello' They shouldn't be a member of the db_owner role after this, unless it's set somewhere by default to add any new users to the db_owner role. This should ...


3

This is an older question, but there are some things that were not explained well and this will hopefully shed some light. The how to shrink was answered, mostly, but this will explain the "why" part of what you are actually doing. Backups, specifically log backups, do several things. The data is written to disk as a backup set to be used or discarded ...


1

do the following it will make your work easy: open SQL Server as SA account click on create new query and past blow queries and click on execute! done. alter authorization on schema::[db_datareader] to [dbo] alter authorization on schema::[db_datareader] to [db_datareader] alter authorization on schema::[db_datawriter] to [dbo] alter authorization on ...


0

In my case this example worked without error, thanks Ben Thul: import-module sqlps -disablenamechecking; $jobs = Get-ChildItem sql\ServerName\default\jobserver\jobs foreach ($job in $jobs) { Write-host $job.Name #script(); $job.script()|out-file c:\out\jobs\$job.sql UTF8 } import-module sqlps -disablenamechecking; $StoredProcedures = ...


2

Once you realize that SSMS is using SMO (Server Management Objects) to do the scripting, and that you can use SMO yourself directly through something like powershell, this sort of thing gets easy. For instance, here's scripting out all the jobs on your server (written in powershell): pushd; import-module sqlps -disablenamechecking; popd; $s = new-object ...


0

I would recommend that you would only add the old instances as data sources from inside SQL Management Studio -that uses a more generic connection method opposed to the direct connection via SQL Management Studio, this will not have all the functionality but you will still be able to access the data. You can also try to open SQL browser on both ends, have a ...


0

This is normally performed using the "Reporting Services Configuration" tool, and navigating to the Windows Service Identity page to make the change.


0

You won't be able to "use" the log-shipped version of the database on the secondary server in this way. You may be able to run select statements to retrieve data from it using the SQL Server Management Studio, but actually running the Reporting Services component of SQL Server from it will not be possible. When running, SSRS may actually insert or update ...


0

This is an answer to the bounty rather than the original question. I think these are two different problems. NitroxDM was experiencing Error Number: 18456, Severity: 14, State: 1. State 1 now occurs when a login is disabled - but actually, the error in the log is 18470, not 18456 - because the login is disabled, it doesn't get that far. See ...



Top 50 recent answers are included