I am new to sql server world as I am a controls engineer who is being asked to manage an asset management system at our facility. We have a system that uses SQL 2005 Express. My database is on drive C, but it is only 10gig and it is running out of space. I have a 210 GIG hard drive as drive D. What is the easiest way to move the database from C to D?
View 18 RepliesBeing a very novice SQL Server administrator, I need to ask the experts a question.
How do I go about moving a database from 1 drive to another? The source drive (C is local to the server, but the target drive (E is on a Storage Area Network (SAN), although it is still a local drive for the server. I want to move the database from C: to E:. Can someone provide me with instructions?
Thanks,
Rick
Hello all -
I have TFS installed on one machine, and the SQL Server database on another. I made the unfortunate mistake of installing SQL Server to the OS drive (C : ), so the TFS database is writing to this drive. How can I switch this to write to another drive (e.g. E:)?
thanks
We installed MS SQL Server to our drive D drive E was the CDROM Drive.We wanted to move the CDROM drive to drive D and the hard drive to driveE. We change that around and corrected the registry entries -repointing everything to drive E instead of D. SQL Server however willnot start it says it cannot find the databases. Where is thisinformation stored. How can I go about changing it?~Todd
View 2 Replies View RelatedHowdy y'all! :)
I have been instructed to move a large database we have on one of our servers off the current drive (local RAID-5 driveset in the server) to a EMC "drive" (logical drive, off-server).
I know one option is to back up the database, delete the database, re-create the db using the new drive for data/log files, then restore the database.
However, I was wondering if it would be better to just detach the DB, move the data/log files, then reattach to them?
Is it half-doz of one, and 6 of the other?
How should I go about this dastardly deed?
Off to poke around in BOL, but thought I would post first in case it's an incredibly easy answer for y'all
Thanks!
I have a Windows 2003 server with SQL Server 2005 installed. Theserver is on small drive and we would like to upgrade to much largerharddrives. I've been hearing of problems using Ghost to get an imageand placing the image onto the new drive. I think this is more of aWindows 2003 problem, but this server is for nothing but the SQLServer databases. Does anyone have a clear method of moving thisserver to the larger drives?TIA.
View 3 Replies View RelatedHi
I have a database(CEB) and my CEB.mdf is on D Drive and CEB.LDF is on
G DRIVE ...NOw I want to move the CEB.LDF on to the different drive ..
can any one suggest me the way and will I have any effect on the database.
It is kind of urgent.
Thanks
RAGHU
Hello All,
Can anyone be so kind as to turn me on to a script to move a database from spilt drives C: and D: to just drive D:. (we have one of those Dell's that comes with C/D partitions so we split the .dta files with a limit on the primary file, but the damn C: drive still ran low on disk space and now we can't install Win 2003 SP2 on it!)
thanks in advance
Bill
I currently have about 4 databases on our SAN located in one of the drives. These databases are going to expand massively and I want o seperate 1 onto seperate drives located on the SAN. I figured using SQL Server Management Studio I could complete this with an easy "Detach / Attach" operation. When I go to attach the files back into SQL, it doesn't read any other drive other than the current drive all of the databases are located on.
Is there a way to do this?
I currently have about 4 databases on our SAN located in one of the drives. These databases are going to expand massively and I want o seperate 1 onto seperate drives located on the SAN. I figured using SQL Server Management Studio I could complete this with an easy "Detach / Attach" operation. When I go to attach the files back into SQL, it doesn't read any other drive other than the current drive all of the databases are located on.
Is there a way to do this?
Hi,
I'm trying to move the transaction logs of my databases to a different drive (for fault tolerance). I can create a second transaction log file for each database via Enterprise Manager but I have 2 questions:
1) If two transaction log files exist for a database which one does it use ?
2) How do I force SQL to use the new transaction log file ? (so I can delete old)
Thanks,
Tim
Hey guys i want to relocate my database datafile and transaction logs from C: drive to D:
From what i have in mind , correct me if i am wrong: First I will create the same folder on D drive as they are on C drive then copy the datafile from C to D , then come back and change the paths on the database files to point on D.
I am trying to find out if it is possible to move indexes to a separate filegroup/disk drive during database restore. I am trying this to see if it improves performance. Also if I cannot move the indexes during restore, how would I move them afterwards to a different filegroup/disk drive? Thanks in advance for all the help.
View 7 Replies View RelatedHello all ...
is there a standard procedure or document that explains how to:
Expand tempdb onto a faster drive ... making it larger
then ...
Remove the small portion of tempdb from my c: drive to reduce contention?
Thanks!
Doug
I want to move all indexes into new separate drive for this I need to create new .ndf file in particular drive.
Mirroring has configured for the DB but the principal and mirror servers do not have same drives.
I want to move indexes to new drive and the derive is not present in mirror server.
I have a database [CarlosDB] that currently has it's .MDF on E: and I need to move the x2 .NDF data files off C: to E:data using a single T-SQL statement:
Code:
database_id file_id db_name disk_path status size read_only
----------- ----------- --------------------------------------------------------------------------------------------------------------------------------
7 1 CarlosDB E:dataCarlosDB.mdf ONLINE 384 0
7 2 CarlosDB_log L:logsCarlosDB_log.ldf ONLINE 128 0
7 3 CarlosDB_2 C:sqlCarlosDB_2.ndf ONLINE 128 0
7 4 CarlosDB_3 C:sqlCarlosDB_3.ndf ONLINE 128 0
(4 row(s) affected)
Looking at the file configuration above, what would be the most logical way as a DBA / SQL Server 2014 Std to move the NDF files to live w/ the MDF file using:
Code:
EXEC master.dbo.xp_cmdshell 'copy c:sqlCarlosDB_2.ndf e:dataCarlosDB_2/ndf'...
but cleanly using a single T-SQL statement? properly formatting a single T-SQL query to use the xp_cmdshell system stored procedure.
We are seeing very high Average Disk Queue Length numbers in one of our clusters (both nodes of the cluster are Virtual, but have their own dedicated virtual environments). Our main data drive also houses TempDB, which I would like to move.
Each node in the Active/Passive cluster are running Windows Server 2012 Standard 64bit and SQL Server 2012 Enterprise 64bit. There is a separate drive for Log files and data files.
The data files also have TempDB on them as previously mentioned. I am reading that you can set up a local disk on each node of the cluster, with the same drive letter and path and then move tempdb as you would with a stand alone SQL Server.
I created the db with the attached script and I am able to access ituntil I reboot the server. I've tried enabling flag 1807 via the SQLserver service and the startup parameters of the instance. In allcases the database always come up suspect after a reboot. There wasone instance where I was able to recover, but I am not sure how thathappened.Does anyone have an idea of how I can reboot the server without thedatabase becomming suspect?USE MASTERGODBCC TRACEON(1807)GO--DBCC TRACEOFF(1807)--DBCC TRACESTATUS(1807)GOCREATE DATABASE ReadyNAS ON( NAME = ReadyNAS_Data,FILENAME = '\NAS1NASDiskSQL ServerReadyNASReadyNAS_Data.mdf',SIZE = 100MB,MAXSIZE = 20GB,FILEGROWTH = 20MB)LOG ON ( NAME = ReadyNAS_Log,FILENAME = '\NAS1NASDiskSQL ServerReadyNASReadyNAS_Log.ldf',SIZE = 20MB,MAXSIZE = 100MB,FILEGROWTH = 10MB)
View 5 Replies View Related
I need to create a SQL server database and add some tables to it. Then access it with a C# application. The problem is that the new SQL server database and it's tables must reside on an external hard drive. How do I point SQL server to this external drive, so that I can create a database on this drive and then create tables and access data on it?
I have 2 different servers that run nightly backup jobs to a network drive using the UNC format. I am noticing the larger databases encountering the following errors on a regular basis
Error: 18210, Severity: 16, State: 1.
'\fnfssql3SQLBackupsMNSQL05<database>.BAK'. Operating system error 64(The specified network name is no longer available.).
BACKUP failed to complete the command BACKUP DATABASE <database>. Check the backup application log for detailed messages.
There are 5 databases on this server all backed up by the same job and 3 of them wortk fine and 2 of them fail so it is not a permissions problem. Have there been any problems with backing up to a network drive in 2005?
I am trying to move a database which I wrote in SQL Server 2005 to a SQL Server 2000 database.
I'm not sure the best way to do this.......
Can anyone enlighten me?.....
I have a SQL Server 2005 Express database on my local machince called OpenAssess.mdf. The server we host with has a file extension of .mdb. How can I go about getting my database to the server? I tried changing the extension to mdb on the local machine but then it tried opening the database in MS Access and didn't work. I just need to connect to the database in my web pages. Here is my connection string and then the error which is visible at the botton of openassessment.org.
*********************************************connection string*************************************************
OPEN_Conn = "Provider=SQLOLEDB;Data Source=connectionToHostServer;Network Library=DBMSSOCN;Initial Catalog=OpenAssess.mdb;User ID=myuserid;Password=mypassword"
*****************************************************error*********************************************************
Microsoft OLE DB Provider for SQL Server error '80004005'
Cannot open database requested in login 'OpenAssess.mdb'. Login fails.
hi guys
i got few questions. i need to move a databases from old server to new server. old server has 25 user databases total datafile around 300GB. heres the questions.
1. what is the fastest way to move all the data to new server? and what's the best way to do it? (DTS? MDF copy over/attach? bak copy over/restore? other theres other way?)
2. i got alot of job and user need to transfer over. i know DTS can do the user.. how about the jobs?
3. do i need to move the master and msdb over too?
4. beside all 3 questions above... do i miss anything that need to be move too?
Thanks guys!!!!!!!!
Hi,
I have a database that resides on a server that`s become too old. It spans
2 devices that sit on 2 different drive letters - D: and E:.
I bought a new server, installed and configured NT4.0 and SQL6.5.
Initially I restored the database to the new server from a dump .It worked
fine, however all the login information was lost. Then I tried partitioning
the new server the same way as the old one and copying all the DAT files
over. Thus I was hoping to retain the information contained in the MASTER.DAT,
drop the database, repartition to create 1 physical drivewith 1 database device,
and restore from a dump to it.
After copying the DATs, though, SQL Server would not start.
Help Please!
I am not a SQL person. I want to copy/move a SQL datbase from old server to a new server and eventualy bring the old server down. What is the procedure to do it. Thanks in advance.
Navid
Hi all. I know that since you know nothing about my database it will
be a stretch to answer this - but does anyone have a boiler plate
checklist for moving a database, dts packages, agent jobs, etc...from
one server to another? Maybe something that just says I should at
least do x,y,z.
Also if anyone out there has any hard won experience/advice about
gotchas when doing this I would love to hear it. We have outgrown a
server and are installing a new one this week that we need to move
over to.
Thanks!
Sql Server 2000 is running on machine havivng two HDD. The HDD where SQL Server resides is reaching capacity. Only 3Gb is remaining. I want to move SQL Server database to other hard drive so that space problem would not occure. How to do it?
View 1 Replies View Relatedi need help moving a database to a new server.
I have an existing database on a Windows XP Pro box running MS SQL Server Desktop Engine 8.00.
I want to move this database to another machine running Windows Server 2003 Small Business Server w/full SQL Server (new edition).
I can see the database, and the directory structures are almost identical on both machines. But when I simply copy the data over nothing works. Obviously to me I must somehow back up the original database and restore it somehow on the new machine.
Any tips on where I begin? I have done searches in the Microsoft Knowledgebase for articles on how to backup and restore from one type SQL to another with frustrating results. No clear directions.
Thanks!
I have system database and user database file are present in G,H and W drive.The process is going to be - copy data from G to S, H to T, W to U. Rename G to X, H to Y and W to Z. Rename S to G, T to H and U to W. Reboot the servers. The original G, H and W will then be X, Y and Z. The old S will be the new G, old T will be H and old U will be W. My question is that after doing this whether my SQL server will start or not
View 8 Replies View RelatedHi
I have to copy (move) a database from one server to another .
One of the way of doing it is to take backup at source server and restore it at destination server .
I am doing it with the following series of statements .
================
At Source Server
================
USE master
EXEC sp_addumpdevice 'disk', 'DBName_Device',
'Irhahadb01F$mssqlackupDBName_Device.dat'
BACKUP DATABASE DBName TO DBName_device
=====================
At Destination Server
=====================
--Copy file (DBName_Device.Dat) from Source backup folder to Destination Backup folder
USE master
EXEC sp_addumpdevice 'disk', 'DBName_Device',
'Irhadvdb02D$mssql7ackupDBName3_Device.dat'
RESTORE DATABASE DBName
FROM DBName_Device
WITH RECOVERY,
MOVE '<Data File Name without .mdf>' TO
'irhadvdb02D$mssql7data<New Data File Name>.mdf' ,
MOVE '<Log File name without .ldf>' TO
'irhadvdb02D$mssql7data<New Log File Name>.ldf'
Above step works fine for one of the test database which small in size.
But it fails for the large database having Data file (.mdf) as 2.5GB and log file as 1.5GB .It says " not enough space on network drive to restore database" . But fact is that I have 200 GB free space on the server .
Please advice .
Sujit
860 520 7454
Hi all. I know that since you know nothing about my database it willbe a stretch to answer this - but does anyone have a boiler platechecklist for moving a database, dts packages, agent jobs, etc...fromone server to another? Maybe something that just says I should atleast do x,y,z.Also if anyone out there has any hard won experience/advice aboutgotchas when doing this I would love to hear it. We have outgrown aserver and are installing a new one this week that we need to moveover to.Thanks!
View 2 Replies View RelatedHi,
I'm developing a website using the new authentication system from asp.net 2.0 and when I try to copy the database to my server and I try to add data to it, it gives me a read-only error.
I've tried several ways, but I can't seem to find the solution. It works well in my computer but if I move it to the server it just doesn't work.
Is there anything I need to do? I have all the permissions needed in IIS.
Thanks,
Bruno Silva
Hi All, first post.
I have done a bit of searching around and cant find a clear answer to this question.
Current Setup
Desktop application (c#) that connects to a SQL Server 2005 express database on the same local network as the application (currently 3 users)
It is only a very small company and has just taken on their first remote worker, but expects to take on another 6-8 over the next few months. They have asked for the database to be moved online.
The application was written in such a way that everything has been done using no stored procs, or views, it is all native SQL.
This will be my first DB hosted online and before I go ahead and do anything I just wanted to make sure what I have to do is correct, sorry if this is a very basic question, although I have been programming for a long time, I have never had the chance to do any online databases before.
Will this work.
1.Find a SQL Server 2005 Hosting company.
2.Move the database to the server.
3.Setup the users permissions.
3.Alter the connection string in the application to point to the new location.
So the only thing that would change would be a new connection string in the application preferences?
Or am I living in a dream world, because nothing is ever that simple.
One thing I am worried about is the security/visiblity of the database and data as it travels from the server to the client and back.
Thanks for any advise you can give.
Mark