You can view the prerequisites here: http://msdn.microsoft.com/en-us/library/ee240731.aspx

Windows Installer 4.5

.NET 4

Microsoft SQL Server Transact-SQL ScriptDom (part of the SQL Server 2014 feature pack which is probably why it keeps taking you...

Scale-out deployments of Reporting Services is an Enterprise Feature. Standard Edition will not work as is stated in the error message you received.

The requirements are listed here: http://technet.microsoft.com/en-us/library/ms156453(v=sql.90).aspx

I have...

Alright, now we are getting some where. If you are using cdc, you should enable and run the CDC jobs. There should be capture and cleanup jobs. The capture job...

Since you ran the stored proc to remove replication, it might be that Change Data Capture may be enabled and the SQL Agent jobs are not running. What does the...

These should answer you questions.

Upgrade Integration Services Packages - http://msdn.microsoft.com/en-us/library/cc280546(v=sql.110).aspx

Upgrade Integration Services Packages Using the SSIS Package Upgrade Wizard - http://msdn.microsoft.com/en-us/library/cc280547(v=sql.110).aspx

You can find what the transaction log is waiting on by running the following and replacing <dbname> with the name of the database in question. This should point you in...

Could it be that the file name is different?

L:\MSSQL\Log\Staging_log.ldf'

VS

L:\MSSQL\Log\Staging.ldf'

Yes, the net_transport column of sys.dm_exec_connections will let you know if the connection is named pipes. It actually shows up as "Named Pipe".

Sounds like the users AD login is the database owner and thus dbo. Run the following to change the database owner to sa and then grant the user's AD account...

Have you tried sp_changedbowner?

EXEC dbo.sp_changedbowner @loginame = N'sa'

GO

http://technet.microsoft.com/en-us/library/ms178630(v=sql.110).aspx

Failing over from a previous version of SQL to a newer version of SQL is a one-way trip. You cannot failback from SQL 2014 to SQL 2008 since the database...

You can attach the database using CREATE DATABASE FOR ATTACH_REBUILD_LOG.

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

If that doesn't work, you can try the undocumented FOR ATTACH_FORCE_REBUILD_LOG.

CREATE DATABASE <YOURDBNAME>

ON (FILENAME = 'D:\<YOURMDFNAME>.mdf')

FOR ATTACH_FORCE_REBUILD_LOG

I've seen this happen when processes spawn multiple SPIDs in an ERP system. It creates a situation where there is no deadlock but also no way to resolve the conflict...

If you have added a login to SQL Server you can query either sys.syslogins or sys.server_principals to see the SIDs.

The SQL login SIDs need to match but SQL Server gets the SIDs for domain users from active directory so it is the same everywhere.