Recovery :: Configuration Option User Options Changed From 0 To 0
May 12, 2015
I'm trying to execute backup job on secondary replica on clustered server(with HA) and I getting the error:execution failed see the maintenance plan and sql server agent job history logs for details.When I going to see the log, it says :configuration option 'user options' changed from 0 to 0.
One of the configuration options that can be set for the server is called "user options". User options contains sub-options such as ansi_warnings, ansi_padding, ansi_nulls, arithabort, etc..
Using T-SQL, how are these set?
sp_configure 'user options', @configvalue = 'value' go reconfigue with override go
i.e. Are the individual option values summed. Say I wanted to set ansi_warnings (whose value is 8) and ansi_nulls (whose value is 32) on and all other user options off. Then is my @configvalue 40?
Sorry, but I don't feel BOL is clear on how to set these options.
I installed SQL Server 2012 on a windows server 2012 that had an existing 2008 R2 SQL installation.
After the install I can see only the 32 bit network configuration options in SQL Server Configuration Manager for both versions. Before the install they were available in the 2008 R2 version of the tool.
I have added several SqlDataSource controls to my C# project, but when I try to configure them, there seems to be a lot of greyed out buttons. Either the WHERE, ORDER BY, and ADVANCED buttons are greyed out, or when they are active, the ADVANCED button always displays the advabced options which are always greyed out. I doesn't make any sense to me. Please explain (in baby language please)
I have a file backup of a database from machine 1. I create an empty database with the same name on machine 2 and copied the backup file to machine 2. When I run a restore database, I get "Preceeding restore operation did not specify WITH NORECOVERY OR WITH STANDBY.Restart tehe restore sequence, specify the options for all but the final step. Restore failed"
Database : SQL 7.0 Trying to restore from the Enterprise manager
I'm trying to implement a sp_MSforeachsp howvever when I call sp_MSforeach_worker I get the following error can you please explain this problem to me so I can over come the issue.
Msg 16958, Level 16, State 3, Procedure sp_MSforeach_worker, Line 31
Could not complete cursor operation because the set options have changed since the cursor was declared.
Msg 16958, Level 16, State 3, Procedure sp_MSforeach_worker, Line 32
Could not complete cursor operation because the set options have changed since the cursor was declared.
Msg 16917, Level 16, State 1, Procedure sp_MSforeach_worker, Line 153
Cursor is not open.
here is the stored procedure:
Alter PROCEDURE [dbo].[sp_MSforeachsp]
@command1 nvarchar(2000)
, @replacechar nchar(1) = N'?'
, @command2 nvarchar(2000) = null
, @command3 nvarchar(2000) = null
, @whereand nvarchar(2000) = null
, @precommand nvarchar(2000) = null
, @postcommand nvarchar(2000) = null
AS
/* This procedure belongs in the "master" database so it is acessible to all databases */
/* This proc returns one or more rows for each stored procedure */
/* @precommand and @postcommand may be used to force a single result set via a temp table. */
declare @retval int
if (@precommand is not null) EXECUTE(@precommand)
/* Create the select */
EXECUTE(N'declare hCForEachTable cursor global for
Hi All, I want to deploy my reports in a Sharepoint site. So I need to change the Deployment mode from Native to Sharepoint Integrated mode. When go to Reporting Services Configuration and in Database Setup - the Server Mode option is not visible. Anyone help me what is the reason for this or How to get Server Mode option in Database Setup in Reporting Services Configuration menu. However the system installed with Sharepoint and SSRS SP2.
Disaster Recovery Options based on the following criteria.
--Currently running SQL 2012 standard edition --We have 18000 databases (same schema across databases)- majority of databases are less than 2gb-- across 64 instances approximately --Recovery needs to happen within 1 hour (Not sure that this is realistic -- We are building a new data center and building dr from the ground up.
What I have looked into is:
1. Transactional Replication: Too Much Data Not viable 2. AlwaysOn Availability Groups (Need enterprise) Again too many databases and would have to upgrade all instances 3. Log Shipping is a viable option and the only one I can come up with that would work right now. Might be a management nightmare but with this many databases probably all options with be a nightmare.
I apologize in advance if this has been posted but if you get the attached error "The record has been changed by another user...", we've discovered that this error can occur if you have a SQL Server Data Type of "Float" and also a "Text" Data Type in the same table. We discovered that it only happens on some records though and I am not sure why this is so. The solution is apparently to add a TimeStamp Data Type to the SQL Server table which does seem to fix the problem. If anyone has any insight on any other solutions (we cannot change the Data Types) or the reasoning behind this error, I would greatly appreciate the feedback.
Dear AllI have a problem ,as i created the new user itspassword became changed.I logon SQL Server as[color=blue][color=green]>> Server Name: localhost>> Server option : window athentication[/color][/color]then i created a new user[color=blue][color=green]>>user name = test>>password = 123[/color][/color]then,i refreshes the serveras i click on the test userits password become too long as ************what is the reason
There is a lot of documention concerning data(base) backups, but I could not find information about how to backup a complete SQL Server instance (data + configuration) or the SQL server configuration (= everything, that is not user payload). you always re-configure your system after restoring, especially because you will forget some settings?I found following things necessary to backup configuration:
server-wide: security: login, roles, ... server objectsserver properties (e.g. collation, connection or memory settings; see SSMS "Server - Properties") per database database settings (SSMS - database - properties)scheme
1. Is there anything missing?In case of a severe system crash I would like to be able to recover the system using a full system image of the virtual machine. However I just create these images after significant changes (e.g. Windows service pack).The SQL server should be backuped independently from these system images.
2. Even if I used SQL Server maintenance plan, choose "backup all databases" and additionally backup resources DB manually I think, that some configuration is still missing, right? Where are the security configuration and server properties saved? In my system database there are some tables, but there is very little content inside, so that the data from the views INFORMATION_SCHEMA* and sys.* obviously is not saved there.SQL Server system objects, such as sys.objects, are physically persisted in theResource database, but they logically appear in the sys schema of every database. URL....What does that mean: Are all DB/table schemes, logins, ... saved in resource DB?
3. Does a usual SQL Server full database backup also contain all settings concerning this database (database properties, logins, ...)?
4. Is there at least a way to backup ONLY the configuration (server-wide and database) without data? The only tool I could find is DACPAC, that exports a database's scheme and some other configuration, but e.g. the database properties are not included: By default, the database created during the deployment will have the default settings from the CREATE DATABASE statement. The exception is that the database collation and compatibility level are set to the values from the source database. URL..
I am getting the following error while trying to update a SQL Server 7.0 table thru' MS Access('97 version). It was working fine until now. This problem started happening after re-linking the table to MS Access as new columns have been added on the SQL Server table. We tried re-starting the MS Access,re-linking the table again,giving all the permissions to the user on the table etc. Also, no other user is accessing the table at the same time..Any help?
Error message in MS Access:
This record has been changed by another user since you started editing it. If you save the record, you will overwrite the changes the other user made.
Copying the changes to the clipboard will let you look at the values the other user entered, and then paste your changes back in if you decide to make changes.
I had a failover occur last night on my AlwaysOn AG, the SQL accounts had to have the passwords re-entered in order to connect to the databases?
1. I checked the SIDS, they match 2. both accounts have sysadmin rights, I know, I don't like it either but the apps will not run without it. 3. Only a few people have access to the SQL servers, right now, they all deny changing the password,
I am trying to install SQL Server 2014 on W10. SQL Server installed, but failed to create a server that be connected to. SQL Server Configuration Manager has no options for creating a server either. How do I create the server.
I'm developing an custom dataflow transformation task that involves mapping of columns between multiple inputs and outputs. All the mappings are stored in a dataset. At first I thought to store this to an variable but after reloading bids I get an schema not found on xml for the stored dataset. Then I tried to put the dataset into an custom property but that seems to only take strings.
So how do I save the info on the mappings contained in my dataset (as that is most easy while using a datagrid to display mappings) in the package preferably in a way that is not visible to the user.
In short: What is the proper way to save complex datatypes in a custom dataflow task using a custom ui?
- When I disable "allow remote connections to this server" from server properties>connection page, I can still remotely connect to the server from SSMS...so what is the impact of enable/disabling it?
- what is the impact of changing the remote query timeout (on the same page) from default value?
Hi I'm a newbie with a problem. SQL Server 6.5 SP4. Have had problems today with SQL Server running out of LOCKS. We increased these & all seemed fine. LOCKS ranout again & we brought SQL Server back up our major database started a recovery. I know the spid of the recovery from the SQL Server errorlog but when I select the sysprocesses table I don't find an entry for this spid. The recovery has been running for about 2 hours. My question is should I see the spid of the recovery process in the sysprocesses table & is 2 hours long for a recovery of a 5 GB database?
Yesterday a user has run a storedprocedure which updates a very transaction table having million of records , as usual the user killed the process in the middle of the execution.(which has resulted in rollback action).
this rollback process blocked other scheduled jobs and its was running for more than 8 hours without completing
as usual decided to shutdown and restart the sqlserver while restarting the sql server went into automatic recovery
the following are the log recording
2001-04-17 12:00:01.86 spid9 Recovery progress on database 'ISH' (7): 48 percent. 2001-04-17 12:00:37.89 spid6 Using 'xpstar.dll' version '1998.11.13' to execute extended stored procedure 'sp_MSgetversion'. 2001-04-17 12:02:36.60 spid9 Recovery progress on database 'ISH' (7): 49 percent. 2001-04-17 12:08:12.79 spid9 Recovery progress on database 'ISH' (7): 49 percent. 2001-04-17 12:11:49.90 spid9 Recovery progress on database 'ISH' (7): 50 percent. 2001-04-17 12:11:50.32 spid9 Recovery progress on database 'ISH' (7): 92 percent.
if you see the log reading from 50% jumps to 92 % and the automatic recovery process is running from another 5 hours (now not able to open the database)
in order to avoid the sql server going into automatic recovery mode (usually the dba use to update the master.sysdatabase table the status column with some magic number to set the database into emergency mode) but i followed my own style (deleting the reocord for the user database from sysdatabases) and restarted the sql server , and used my monday tape backup (complete bkup) to recover the database. In the recovery option i used force restore over existing database (hoping that this will reduce the database recovery time ,bcaus the data file (mdf and ldf ) need not to be created.
but the result :- after running six hours of loading data from tape ( i am getting the following reading in the log file)
realy do not what is happening in the background.(if its oracle the dba has the control over the database . In sql server has the control over the dba)
any one who has any idea on sql server recovery (the size of the database is 22 gb which is recovered and tape device is hp sure store DAT 40 E (DSS-4,4MM TAPE). Thanks in advance
1Is it possible to choose local user,(instead of local system) in sql setup service login and then use mixed mode default configuration in report server or choose configure server later. I will be using a third party host using vista, unfortunately I do not have my own server ( I do not have a domain yet) vista sql 2005 standard vs 2008. ultimate 2 What is the best configuration for a new aspiring asp.net ssrs developer. 3 Do I need to configure the server if I choose local user? 4. what is the best way to configure sql?
By the way what items should I look forward in choosing a web host,(who is willing to give alot of help to developers) my interests include ssrs 2008 sql 2008 sql 2005 asp.net mvc, crystal reports, wcf infragistics. I am really interested in showing examples in sql reporting services, crystal reports wcf , web services , infragistics asp.net mvc intrigues me....... I would like to get on a track to eventually use sharepoint services Thanks again, I know I ask I alot of questions........
How to find last login date/time for user DML acitivity on databases on Instance?
Is there any way we can find our the last login date/time for databases?
Note: 1. We can find if the SQL Trace is running and store.This is not good solution 2. Audit logins off/on is also not good solution. 3. Using DMV's also not good option, if reboot sql server instance then historical values can not see.