Is this a development database on a dev server?

It all depends on how much work the IndexOptimize job has to do. One way to check would be to run the following script:-

USE [<DB NAME>];

GO

SELECT

DB_NAME(DB_ID()) AS [Database Name],...

What I would do is grant the user SELECT on the sys.server_principals table in the master database. This will allow the user to see all the logins.

I would then make...

To check if the account is enabled, open SSMS go to Security > Logins. Right click the sa login and go to Properties > Status.

You'll then be able to see...

There's a function in SQL Server called ROUND():-

http://msdn.microsoft.com/en-us/library/ms175003.aspx

Once you've got your new SQL installation setup you have several options for migrating your databases. You've already mentioned backup and restore, there's also mirroring and log shipping too.

If you...

I've used http://databasehealth.com/ in the past as a free tool. It works fairly well just be careful with it as it creates jobs on the target server(s).

There's also the PAL...

Not sure if you're still watching this post but I would check that the SQL Server Agent account has permissions to the directory.

As you're running the backup as a job...

Microsoft release a free PDF called 'Introducing SQL Server 2012' which should help you get started.

It can be found here:- http://blogs.msdn.com/b/microsoft_press/archive/2012/03/15/free-ebook-introducing-microsoft-sql-server-2012.aspx

Did you restart your local instance after the deadlock occurred?

If you did, the deadlock information would be contained in one of the other error log files:-

ERRORLOG.1

ERRORLOG.2

etc

Have you looked in those...

With trace flag 1222 running the deadlock information will be recorded in the SQL Server log.

Open up SSMS, then got to Management > SQL Server Log. Then open the log...

Rebuilding indexes will consume disk space, but I would recommend that you backup the log regularly instead of switching the database's recovery mode.

Why are you switching recovery modes to perform maintenance on your indexes?

From MSDN:-

Specifies that if the configuration setting does not require a server stop and restart, the currently running value should be updated.

You've already run RECONFIGURE so don't worry. Best way...

The way I would do this is:-

--Create table

CREATE TABLE Ticket

([Ticket] CHAR(1),

[User] CHAR(3),

[Priority] TINYINT);

GO

--Insert data

INSERT INTO dbo.[Ticket]

SELECT 'A', 'ME', 1 UNION ALL

SELECT 'B', 'ME', 1...