|
|
|
|
||||||
| ms.sqlserver.setup Questions about SQL Server. |
![]() |
|
|
LinkBack | Outils de la discussion |
|
|
#1 |
|
Messages: n/a
Hébergeur: |
Hi,
Let me describe my situation first. I am developing a database using Access and now planning to move a step further to use SQL Server 2000 as back end. I don't want to mix up with the Network Administrator over the security password to the Server. My question is as follow: 1 - after installation, can I create/develop the database and manage login remotely from my workstation by having SQL Personal Edition install on my PC (without being physically standing in front of the Server)? 2 - Can I backup the database from my workstation by connecting SQL PE to the server. (I doubt that I may need the password as well) TIA SF |
|
|
|
#2 |
|
Messages: n/a
Hébergeur: |
If you are using SQL Server you do not need to have Personal Edition on your
machine to administer a server -- you just need the SQL Server client tools. SQL Server 2000 ships with Enterprise Manager and Query Analyzer which allow you to do pretty much anything that you need to do (including creating databases, creating objects within databases, managing security, and performing backups). When you move to SQL Server 2005 you will notice that EM and QA are gone. They have been replaced by one tool - SQL Server Management Studio (SSMS). You can backup the database on the server and restore it to your machine. I recommend that you read up on BACKUP and RESTORE within Books Online. In a nutshell you will need to --run this when connected to the database server from your computer (use Query Analyzer) BACKUP DATABASE foo TO DISK = 'x:\foo.bak' WITH INIT --run this when connected to SSPE (again, use Query Analyzer) RESTORE DATABASE foo FROM DISK = 'x:\foo.bak' Assumptions: You will change "foo" to the name of the database that you want to back up. Drive X exists. If it doesn't change the path to a location that does exist You copied the backup (.bak) file to your computer and changed the drive X reference The database does not already exist on your machine. If it does you will need to use WITH REPLACE Your PC has the same disk drives and paths set up as the server. If not, you will need to use WITH MOVE Please refer to Books Online for more detailed information regarding backup and restore. -- Keith Kratochvil "SF" <ssamnang@yahoo.com> wrote in message news:ec5lZXp8GHA.4348@TK2MSFTNGP03.phx.gbl... > Hi, > > Let me describe my situation first. I am developing a database using > Access and now planning to move a step further to use SQL Server 2000 as > back end. I don't want to mix up with the Network Administrator over the > security password to the Server. > > My question is as follow: > > 1 - after installation, can I create/develop the database and manage login > remotely from my workstation by having SQL Personal Edition install on my > PC (without being physically standing in front of the Server)? > 2 - Can I backup the database from my workstation by connecting SQL PE to > the server. (I doubt that I may need the password as well) > > TIA > > SF > |
|
![]() |
| Outils de la discussion | |
|
|