I'm intrigued, what kind of problems do these guys resolve?

Note I didn't say certified DBAs earlier, experience qualifies a DBA in my book.

Remove the account from Domain Administrators, grant access on the share and the folder to the account the SQL Server is running under.

Trust me, and microsoft, this will work and...

Grant select on sys.dm_tran_locks to applicationrole

--Lock handling shouldn't be written into the application.

Oliver, you appear to be confused about a number of issues so I suggest we get things nice and simple first.

Forget remote connections, let's get an SQL login working through...

Call pervasive, there are odbc drivers available.

Clustering the pervasive client is a more complex operation.

Make sure named pipes is disabled.

Try the connection from a machine that does not have the certificate installed.

It's because SQL 2005 is more secure by default than 2000, so you won't be giving them any more access than they had in 2000.

But to remain secure, as that...

You don't want to use enterprise manager, you want to use SSMS.

And the error is the same locally or remotely?

Check the application log, if there are no entries for failed logins, then your problem is not on SQL Server, if there...

Absolutely, you can create stored procedures from T-SQL or managed code as you like. This would work for example:

CREATE PROCEDURE dbo.usp_testproc

AS

SELECT *

FROM...

You don't need another datbase engine. You should be able to do this through linked servers, it's just a matter of having the right provider.

Try creating a SystemDSN (ODBC...

T-SQL

The main impact will be integration with .Net through the Common Language Runtime (CLR) which means you don't need to write T-SQL anymore (!).

But sticking with T-SQL, you've got new...

BEGIN TRY

{ sql_statement | statement_block }

END TRY

BEGIN CATCH

{ sql_statement | statement_block }

END CATCH

Not sure how else to put it. What errors are you getting?

I believe you meant to say DDL triggers:

CREATE TRIGGER trigger_name

ON { ALL SERVER | DATABASE }

[ WITH [ ,...n ] ]

{ FOR | AFTER } { event_type...

There's too many differences to put into a single reasonable table.

What are you interested in?

Licensing, hardware, new functionality...?