SQL Developers Edition and Windows XP

[moone]

I'm currently running an SQL Developers edition as my database. I can successfully do a daily backup on the production db. I want to have an backup server in case the production goes down. I tried backing it onto another windows XP computer, I get an error, Device is not available. I installed database on both pc but for some reason it only sees the production database drive C. I tried sharing but no soap.

I tried sp_AddDevice
I tried hard coding the path and used the IP address.
Does it have to do anything with the login.

Any suggestions.

Both PC are Windows XP Home/SQL Developers Edition.
This a peer to peer network.

 

[mrdenny]

So you are trying to do a backup to the second PC's hard drive, or are you trying to restore the backup to the second PC's SQL installation?

Denny

--Anything is possible. All it takes is a little research. (Me)

 

[moone]

Yes, I am trying to backup to the second PC. I will restore after I get the back up of the data from the production database.

 

[SQLBill]

One important thing....you say you are using the Developer Edition for a PRODUCTION database...tsk tsk that's not allowed:

Developer edition is designed to allow developers to build any type of application on top of SQL Server. It includes all the functionality of Enterprise Edition but with a special development and test end-user license agreement (EULA) that prohibits production deployment.

It MIGHT be that issue that is not allowing you to do what you want.

-SQLBill

 

[moone]

Does MSDE prohibits production development...

 

[SQLBill]

MSDE is not DEVELOPER version. MSDE is DESKTOP Engine version. They are two different things. Which one are you really using?

Developer Edition has the same functions as Enterprise Edition, but you use it for developing/designing your database(s). Kind of like a test setup.

MSDE (Desktop Engine) can be used in production, but it's a 'watered down' version.

-SQLBill

 

[moone]

I have the specs now.
Computer 1 = SQL Server 7 edition
Computer 2 = SQL Server 2000 edition

On the production database (we'll call this 1st computer) I believe its SQL Server 7 edition. When I first tried manipulating data, I discoverted that I need to install a client tool. I installed the SQL Server 2000 client tool. I am successfully able to see and manipulate the data as well as the stored procedure and backup etc.

But, here in where my problem lies. I want to set up a second backup job to backup onto another computer (we'll call it 2nd Computer) but it does not see the 2nd computers drives or directories. The 2nd computer is going to be my failover server. It will have the same data as production database.

Any suggestions

Mo

 

[MDXer]

THis sounds more like an issue with network and network permissions than a sql issue and again. Developer Edition is just that Develop.

Shoot Me! Shoot Me NOW!!!
- Daffy Duck

 

[SQLBill]

On Computer 1, look in Services. What login does the SQL Server services use? Is it Local System or a Domain account? It needs to be a Domain account to do what you require.

Second, does Computer 1 have access to Computer 2? Test by openning a command window (Start>Run, type CMD and click OK.) Then type PING Computer2 (replace Computer2 with the real name). If that fails, try it with the IP Address. If that works, you'll need to set up name-resolution or use just the IP Address. If neither work, you'll need to check with your system/network admin since you can't connect.

-SQLBill

 

[moone]

I will try that. Thankz
Mo