SQL Server troubleshooting - Revision history

WikiSysop: /* Repairing SQL Server database */

2016-04-19T15:43:39Z

Repairing SQL Server database

← Older revision		Revision as of 15:43, 19 April 2016
Line 23:		Line 23:
	# Find the database under Databases in the Object Explorer		# Find the database under Databases in the Object Explorer
	# Rightclick the database and select: Tasks - Detatch...		# Rightclick the database and select: Tasks - Detatch...
	# Delete the .ldf file so sequal server can't find it		# Delete the .ldf file so sequal server can't find it - sometimes it might be better not to delete it, give it a try!
	# Select: File - New - Query with Current Connection		# Select: File - New - Query with Current Connection
	# Execute query: exec sp_attach_single_file_db '<database name>', 'C:\<path to database>.mdf'		# Execute query: exec sp_attach_single_file_db '<database name>', 'C:\<path to database>.mdf'

WikiSysop: /* Repairing SQL Server database */

2015-01-20T15:32:03Z

Repairing SQL Server database

← Older revision		Revision as of 15:32, 20 January 2015
Line 25:		Line 25:
	# Delete the .ldf file so sequal server can't find it		# Delete the .ldf file so sequal server can't find it
	# Select: File - New - Query with Current Connection		# Select: File - New - Query with Current Connection
	# Execute query: exec sp_attach_single_file_db '~~TRACKMAN~~', 'C:\<path to database>.mdf'		# Execute query: exec sp_attach_single_file_db '<database name>', 'C:\<path to database>.mdf'
	# Rightclick the database and select: Tasks - Detatch...		# Rightclick the database and select: Tasks - Detatch...
	# Rightclick the Databases and select: Attach... and attach the database again		# Rightclick the Databases and select: Attach... and attach the database again

WikiSysop: /* How to resolve the issue of a database that was in Recovery Pending mode */

2014-10-07T12:30:50Z

How to resolve the issue of a database that was in Recovery Pending mode

← Older revision		Revision as of 12:30, 7 October 2014
Line 48:		Line 48:
	NO_WAIT		NO_WAIT
	Specifies that if the requested database state or option change cannot complete immediately without waiting for transactions to commit or roll back on their own, then the request will fail.		Specifies that if the requested database state or option change cannot complete immediately without waiting for transactions to commit or roll back on their own, then the request will fail.

			REPAIR_ALLOW_DATA_LOSS
			Is the repair level that DBCC CHECKDB recommends when it finds corruptions. This is because fixing nearly anything that’s not a minor non-clustered index issue requires deleting something to repair it. So, REPAIR_ALLOW_DATA_LOSS will delete things. This means it will probably delete some of your data as well. If, for instance it finds a corrupt record on a data page, it may end up having to delete the entire data page, including all the other records on the page, to fix the corruption. That could be a lot of data. For this reason, the repair level name was carefully chosen. You can’t type in REPAIR_ALLOW_DATA_LOSS without realizing that you’re probably going to lose some data as part of the operation.

	<google>ENGELSK</google>		<google>ENGELSK</google>

WikiSysop: /* How to resolve the issue of a database that was in Recovery Pending mode */

2014-10-07T12:26:57Z

How to resolve the issue of a database that was in Recovery Pending mode

← Older revision		Revision as of 12:26, 7 October 2014
Line 42:		Line 42:

	This solved the problem.		This solved the problem.

			ROLLBACK IMMEDIATE
			Tells the SQL Server that if it can’t complete the command right away, then the other pending transactions should be rolled back.

			NO_WAIT
			Specifies that if the requested database state or option change cannot complete immediately without waiting for transactions to commit or roll back on their own, then the request will fail.

	<google>ENGELSK</google>		<google>ENGELSK</google>

WikiSysop: /* How to resolve the issue of a database that was in Recovery Pending mode */

2014-05-19T15:02:31Z

How to resolve the issue of a database that was in Recovery Pending mode

← Older revision		Revision as of 15:02, 19 May 2014
Line 33:		Line 33:
	==How to resolve the issue of a database that was in Recovery Pending mode==		==How to resolve the issue of a database that was in Recovery Pending mode==
	* [http://social.msdn.microsoft.com/Forums/sqlserver/en-US/835dee9b-0993-433f-baf7-a646dfa7f8f7/how-to-resolve-the-issue-of-a-database-that-was-in-recovery-pending-mode?forum=sqldatabaseengine How to resolve the issue of a database that was in Recovery Pending mode]		* [http://social.msdn.microsoft.com/Forums/sqlserver/en-US/835dee9b-0993-433f-baf7-a646dfa7f8f7/how-to-resolve-the-issue-of-a-database-that-was-in-recovery-pending-mode?forum=sqldatabaseengine How to resolve the issue of a database that was in Recovery Pending mode]
			Stop SQL Server and remove transaction log file of this DB then restart again where DB should go with suspect mode ….If so you can run the below query

			#ALTER DATABASE [DB_Name] SET SINGLE_USER WITH NO_WAIT
			#ALTER DATABASE [DB_Name] SET EMERGENCY;
			#DBCC checkdb ([DB_Name], REPAIR_ALLOW_DATA_LOSS )
			#ALTER DATABASE [DB_Name] SET online;
			#ALTER DATABASE [DB_Name] SET Multi_USER WITH NO_WAIT

			This solved the problem.

	<google>ENGELSK</google>		<google>ENGELSK</google>

WikiSysop: /* Repairing SQL Server database */

2014-05-19T15:00:31Z

Repairing SQL Server database

← Older revision		Revision as of 15:00, 19 May 2014
Line 30:		Line 30:

	* [http://social.msdn.microsoft.com/Forums/en-US/sqldatabaseengine/thread/290f3875-2c73-4f73-8228-b3713cf7853b/ Database Recovery]		* [http://social.msdn.microsoft.com/Forums/en-US/sqldatabaseengine/thread/290f3875-2c73-4f73-8228-b3713cf7853b/ Database Recovery]

			==How to resolve the issue of a database that was in Recovery Pending mode==
			* [http://social.msdn.microsoft.com/Forums/sqlserver/en-US/835dee9b-0993-433f-baf7-a646dfa7f8f7/how-to-resolve-the-issue-of-a-database-that-was-in-recovery-pending-mode?forum=sqldatabaseengine How to resolve the issue of a database that was in Recovery Pending mode]


	<google>ENGELSK</google>		<google>ENGELSK</google>

WikiSysop: /* Repairing SQL Server database */

2013-01-16T14:47:39Z

Repairing SQL Server database

← Older revision		Revision as of 14:47, 16 January 2013
Line 18:		Line 18:

	==Repairing SQL Server database==		==Repairing SQL Server database==
	. This error may indicate data corruption or that the log file (.ldf) does not match the data file (.mdf).		. This error may indicate data corruption or that the log file (.ldf) does not match the data file (.mdf).<br>

			# Open the database in SQL Management Server
			# Find the database under Databases in the Object Explorer
			# Rightclick the database and select: Tasks - Detatch...
			# Delete the .ldf file so sequal server can't find it
			# Select: File - New - Query with Current Connection
			# Execute query: exec sp_attach_single_file_db 'TRACKMAN', 'C:\<path to database>.mdf'
			# Rightclick the database and select: Tasks - Detatch...
			# Rightclick the Databases and select: Attach... and attach the database again

	* [http://social.msdn.microsoft.com/Forums/en-US/sqldatabaseengine/thread/290f3875-2c73-4f73-8228-b3713cf7853b/ Database Recovery]		* [http://social.msdn.microsoft.com/Forums/en-US/sqldatabaseengine/thread/290f3875-2c73-4f73-8228-b3713cf7853b/ Database Recovery]
	<google>ENGELSK</google>		<google>ENGELSK</google>

WikiSysop at 09:01, 16 January 2013

2013-01-16T09:01:54Z

← Older revision		Revision as of 09:01, 16 January 2013
Line 17:		Line 17:
	* [http://connect.microsoft.com/SQLServer/feedback/details/375231/installing-sql-server-2008-with-user-name-that-equals-computer-name-fails# Installing SQL Server 2008 with user name that equals computer name fails]		* [http://connect.microsoft.com/SQLServer/feedback/details/375231/installing-sql-server-2008-with-user-name-that-equals-computer-name-fails# Installing SQL Server 2008 with user name that equals computer name fails]

			==Repairing SQL Server database==
			. This error may indicate data corruption or that the log file (.ldf) does not match the data file (.mdf).
			* [http://social.msdn.microsoft.com/Forums/en-US/sqldatabaseengine/thread/290f3875-2c73-4f73-8228-b3713cf7853b/ Database Recovery]
	<google>ENGELSK</google>		<google>ENGELSK</google>

WikiSysop at 06:54, 29 December 2012

2012-12-29T06:54:59Z

← Older revision		Revision as of 06:54, 29 December 2012
Line 2:		Line 2:
	[[Category:Software development]]		[[Category:Software development]]
	==Reasons why SQL server installation will fail==		==Reasons why SQL server installation will fail==
	====~~Username~~ is ~~the same as Computername~~====		====A reboot is pending====
	* [http://support.microsoft.com/kb/310845/en-us Error Message: The User Name May Not Be the Same as the ~~Computer Name.~~..]		If something else like a Windows update, ore another program that requires a reboot was installed before SQL server, and scheduled the rest of .dll replacements to happen during next reboot.<br>
	* [http://connect.microsoft.com/SQLServer/feedback/details/375231/installing~~-sql-~~server~~-2008-with-user-name-that-equals-computer-name-~~fails~~# Installing SQL Server 2008 with user name that equals computer name fails]~~		Reboot PC before installing SQL server, if it fails, try to reboot again and try once more.

	====Regional settings not is same as Windows language type====		====Regional settings not is same as Windows language type====
Line 13:		Line 13:
	After installing regional settings can be set back.		After installing regional settings can be set back.

	====~~A reboot~~ is ~~pending~~====		====Username is the same as Computername====
	~~If something else like a Windows update, ore another program that requires a reboot was installed before SQL server, and scheduled~~ the ~~rest of~~ .~~dll replacements to happen during next reboot~~.~~<br>~~		* [http://support.microsoft.com/kb/310845/en-us Error Message: The User Name May Not Be the Same as the Computer Name...]
	~~Reboot PC before~~ installing SQL ~~server, if it~~ fails~~, try to reboot again and try once more.~~		* [http://connect.microsoft.com/SQLServer/feedback/details/375231/installing-sql-server-2008-with-user-name-that-equals-computer-name-fails# Installing SQL Server 2008 with user name that equals computer name fails]

	<google>ENGELSK</google>		<google>ENGELSK</google>

WikiSysop: /* Reasons why SQL server will fail */

2012-12-29T06:54:23Z

Reasons why SQL server will fail

← Older revision		Revision as of 06:54, 29 December 2012
Line 1:		Line 1:
	[[Category:English pages]]		[[Category:English pages]]
	[[Category:Software development]]		[[Category:Software development]]
	==Reasons why SQL server will fail==		==Reasons why SQL server installation will fail==
	====Username is the same as Computername====		====Username is the same as Computername====
	* [http://support.microsoft.com/kb/310845/en-us Error Message: The User Name May Not Be the Same as the Computer Name...]		* [http://support.microsoft.com/kb/310845/en-us Error Message: The User Name May Not Be the Same as the Computer Name...]