Tag Info

Hot answers tagged

15

No, there is no workaround to upgrading a database directly from 2000 to 2012. Since you don't have a ton of data, you can do all kinds of things to move the data (but not the database as a whole), including: Import/Export wizard SSIS BCP Manual queries using a linked server from 2012 or an application However these will not necessarily bring over other ...


6

Stating there is no workaround seems a little premature. You say your database only contains a few tables and views. Why not export the tables and views schema as SQL create statements and run them on your target database? You could then also export the actual data into something like CSV format and import them into the target database, or perhaps even ...


6

is it possible to view the locks, along with the type, acquired during the execution of a query? Yes, for determining locks, You can use beta_lockinfo by Erland Sommarskog beta_lockinfo is a stored procedure that provides information about processes and the locks they hold as well their active transactions. beta_lockinfo is designed to gather as ...


5

This will not be fast (this took over a minute to produce 0 results in my local copy of AdventureWorks). DECLARE @SpecificWord NVARCHAR(32); SET @SpecificWord = N'donut'; DECLARE @sql NVARCHAR(MAX); SET @sql = N'SELECT NULL,NULL WHERE 1 = 0'; SET @SpecificWord = N'%' + @SpecificWord + N'%'; SELECT @sql += N' UNION ALL SELECT ''' + QUOTENAME(s.name) + ...


2

No, you cannot migrate it directly from 2000 to 2012. What you can do is install a temporary instance of 2005 OR 2008 oR 2008R2, restore the 2000 database here. Once done you can now upgrade from installed instance by taking the backup of database from that instance and restoring onto sql server 2012. You will have to make the migration in two steps: ...


2

Here is how I look at locks by process/table/lock type: SELECT HostName, "OS UserName", Login, spid, "Database", TableID, "Table Name_________", IndID, -- [Index Name], "Lock Type", "Lock Mode", Status, -- Resource, Count(*) AS "Lock Count" FROM ( SELECT Convert(VarChar(30), ...


2

The logs led us to review our Cluster services: There was an error to lookup cluster resources. Error: There was a failure to call cluster code from a provider. Exception message: Generic failure . Status code: 4104. Description: . HResult : 0x86d80014 FacilityCode : 1752 (6d8) ErrorCode : 20 (0014) Data: errorMessage = There was a failure to call ...


1

There can be several causes for this error: The backup is corrupted as it has not been transferred in binary mode If you are using FTP to transfer the backup, make sure the file is transferred in binary mode The version of your backup is different than the SQL Server instance you are trying to restore it to. You can try to restore to a SQL server instance ...


1

You can view the locks for a session using sp_lock or sys.dm_tran_locks. In both ways you can filter by the session. You can also use Extended Events to do that.


1

The other alternative would be to use operating system command and give powershell.exe c:/path/script.ps1 as command and save your script in script.ps1. This will ensure using OS powershell instead of using provider.


1

If you want to be able to view the exact backup history for longer time than those four weeks that you keep the backup files on disk, make sure that you set the cleanup task not to delete the backup history from the msdb database, you can then run the backup report from SSMS (right click database, select reports, standard reports, backup and restore events) ...



Only top voted, non community-wiki answers of a minimum length are eligible