First off, enable success and failure auditing in MSDE. Check your application log to see exactly which accounts are being used, and what is failing.

"if I use SQL Server...

Books online and tutorials, http://www.microsoftelearning.com and doing actual deployments.

Okay, well without knowing what dataloss and downtime your business will accept you cannot design an acceptable system.

Without knowing the utilization of the T1 line, or the traffic you will...

Strictly speaking you should create a schema to group the objects, and a role to group the users.

GRANT SELECT ON SCHEMA :: schemaname TO rolename

Any users you don't want to...

'an object' - can you be more vague please?

Perhaps my questions weren't clear;

What does the business require in terms of availability, data loss and recovery time?

--Are they happy losing a maximum on one hours worth of data?...

How many transactions are you expecting?

Although it's an interesting thought experiment, I don't agree with using SQL logins, and I don't agree with anyone but the DBAs restoring databases.

Is there a good reason you want...

Right, I think I see the issue now.

The 'sa' account and your windows account have access to the operating system. Sysadmins use the sql services to access the path...

What is this user account to be used for/by?

Is it specifically creating a new database from a tape backup?

Read the question, Homey:

"I am new to SQL Server.Can somebody suggest a certification program specific to SQLSERVER **developers**?"

Watch these:

https://www.microsoftelearning.com/sqlserver2005/

Read this:

http://go.microsoft.com/fwlink/?linkid=44375

And play with this:

http://www.microsoft.com/downloads/details.aspx?FamilyID=220549b5-0b07-4448-8848-dcc397514b41&DisplayLang=en

(Make sure you meet requirements and also install

http://www.microsoft.com/downloads/details.aspx?familyid=9697AAAA-AD4B-416E-87A4-A8B154F92787&displaylang=en

and

http://www.microsoft.com/downloads/details.aspx?FamilyID=82afbd59-57a4-455e-a2d6-1d4c98d40f6e&DisplayLang=en

)

Enjoy! ))

Before you design anything, you need requirements.

What does the business require in terms of availability, data loss and recovery time? What are their disaster recovery plans (non-SQL)?

Next move to...

What's the message displayed.

There are plenty of other requirements to meet.

Why on Earth would you have a backup system running on a different version of SQL Server?

Did you do the same with 7/2000?