Whenever possible, avoid granting permission to public. If you grant any logins access to a given database, the public permissions would automatically apply. I believe Andy Warren has an article...

Well, keep in mind that the app role must be set by the calling application (through the sp_setapprole stored procedure), if it's not going to do that, there's no point...

Is the client machine's SQL Server set to run as a domain user account or is it running as System?

This sounds like a "double-hop" issue. When a client goes from the workstation to the first

SQL Server, that's the first hop. When you go from the first SQL Server to...

If you're going down that route... follow the Principle of Least Privilege. Only give the rights needed, nothing more.

Don't use db_datareader and db_datawriter. Instead, assign the appropriate permissions. Keep in...

Potentially you can, but it's probably not a good idea. You'd have to be making call to objects with respect to SQL Server 2000 using the sp_OA* stored procedures or...

Is the CRM application and the SQL Server on the same box? Or when you did the restore, is the database now on a separate server from the CRM application?

Tables, yes. You can make the application role a member of the db_datareader and db_datawriter fixed database roles. Stored procedures and functions, no. Everything one of those is created, you'll...

Is neighbor_server the name of your SQL Server?

Does the account you set SQL Server Agent to have a login within SQL Server?

Is is a member of the sysadmin fixed...

I would be hesitant to use names which so clearly identify what the purpose is. I understand it from a manageability perspective, but there is an information disclosure risk...

In a...

They'll also need to own the job or be a member of the TargetServersRole role, though this latter option is not supported by MS. There's code in a view, sysjobs_view,...

or SQL Server Integration Services (what DTS became in SQL Server 2005). There is an import/export wizard you may find helpful in both cases.

This runs from the SQL Server against a domain controller. This assumes the computer's domain because a path to a particular domain or domain controller is not specified. I believe...

Locks don't only keep honest people out. They keep out dishonest people who can't figure out how to bypass the lock. That's a...

Password protected backups in SQL Server 2000 only prevent you from restoring the data. You can open up said backups with a text editor and get the data anyway. Also,...