HOw To Force SQL 2005 To Use My D Drive To Install Files Instead Of C

I Need To Be Able To Install SQL Server 2005 On A Different Partition Besides The C Drive. Thanks

I created two partitions for my hard drive. The C drive which holds all of the Windows 2003 server operating system files and E drive which will be just for data and applications. The C drive is only 30GB while the E drive is 119GB. I need to be able to install in the application on the E drive. I already tried creating a folder on the E partition named program files with the sql2005 folder in it when I go through the installer package. SQL server still wants to be installed on the C drive. Is there anyway I can change this so it gets installed on the E partition. Thank You

Install Sql Server 2005 Workgroup On D: Drive

I am trying to install the SQL Sever 2005 Workgroup Edition software that came with our Small Business Server 2003 R2 system. I would like to install to the d: drive because space on the c: drive is limited. Can I do that? If so, how?

I Need To Be Able To Install SQL Server 2005 On A Different Partition Besides The C Drive

I created two partitions for my hard drive. The C drive which holds all of the Windows 2003 server operating system files and E drive which will be just for data and applications. The C drive is only 30GB while the E drive is 119GB. I need to be able to install in the application on the E drive. I already tried creating a folder on the E partition named program files with the sql2005 folder in it when I go through the installer package. SQL server still wants to be installed on the C drive. Is there anyway I can change this so it gets installed on the E partition. Thank You

Install SQL Server 2005 Express Edition Onto A Drive Other Than C

I am trying to install SQL Server 2005 Express Edition onto my PC on the D: drive. I do not have write privelleges to the C Drive. All I want to do is point the executable to install to another drive like D: or E: etc. Is this possible with SQL Server 2005 Express Edition setup executable file.


Just to let you know I have changed the template.ini file in the source folder to reflect the following (I tried both with and without quotes)


INSTALLSQLDIR="D:Program FilesMicrosoft SQL Server"


And then using command prompt I did the following:


"start /wait setup.exe /qn myini.ini"


and it still doesn't work.

Move Log Files For SQL 2005 Databases To Another Drive

Hello,

I need to move all log files for my SQL 2005 databases to another drive. I don't wish to shrink the files, I need to move the logs to another drive spindle. I did find an article (Article ID: 224071) that describes moving both the database and logs using sp_detach and then sp_attach. What is the best way just to move the logs to another drive on the same server, and that keeps the databases in their original location?
Thanks.

Install SQL 2005 Std X64 From Software Distribution Zip Files?

I've got three files (sql 2005 std edition x64) that were downloaded from the volume license software distribution download site. One appears to be the SP2 (SW_CD_NTRL_SQL_Svr_2005SP2_64Bit_X64_English_1_X13-36347.EXE). But the other two I can't figure out how to handle. I've unzipped them both (SW_CD_SQL_Svr_Standard_Edtn_2005_64Bit_X64_English_1_x64_MLF_X11-57664.EXE SW_CD_SQL_Svr_Standard_Edtn_2005_64Bit_X64_English_2_x64_MLF_X11-57665.EXE) and they appear to have differences in what they contain, BUT there are no instructions on how to proceed with the install. I'm guessing one of them is the 32 bit versions of the management tools that still run in 32 bit mode and the other is the server. The readme's in both are the same. There are no directions on what to do or how to proceed with the installation. I've started both installs just to get far enough to see that they both want to install prerequisite software but neither tells me that this is 64 bit prerequisite. They look identical to that point.

Please point me in the right direction for some instructions on how to install this. I've installed SQL hundreds of times, but this one has be stumped on the proper process.

Update SQL Server 2005 Install Files

Is it possible to update the SQL 2K5 installation files to SP1? Thanks.

SQL 2005 Failed - Cannnot Install Files To The Compressed Or Encrypted..

Hi, I am trying to lean ASP.NET. So I was trying to install SQL Server too. But, I could not install. The aleart box popped up:

"SQL Server set up cannot install files to the compressed or encrypted folder: C:Program FilesMicrosoft SQL Server"

Before this, I also got a warning that the hardware of my computer does not meet the hardware requirement.

I would like to know how I can install SQL Server into my computer. Or, shouldn't I do that? To learn ASP.NET I want to have a database ready. If I can not use SQL Server, I may try Access or something smaller...

Thanks in advance.



yyokota2

Unable To Install SQL Server 2005 - Removing Backup Files Hangs

HELP!

For the past several weeks, I have been trying to install SQL Server 2005 on a Win XP SP2 PC. Regardless of the options I choose (SQL Engine + Client Tools, Client Tools only, etc.) when the installation gets to the end of the Client Tools setup and the setup status displays "Removing Backup Files", my PC appears to hang.

For a period of time, there is a fair amount of HD activity which gives me the impression that files are in fact being deleted, but then there is no HD activity and the installation appears to hang. Finally I give up and kill the setup process and reboot.

After reboot, it appears that the client tools have been installed (the icons appear and I can open the Management Studio, but when I try to connect to an existing instance of SQL, that hangs. This occurs for either Windows or SQL authentication.

Has anyone experienced this behavior and determined the root cause? What EXACTLY is happening during the "Removing Backup Files" phase of the installation?

Thanks for any help in advance,
Marc Mueller

SQL Install - C: Drive

We are currently having a "lively" discussion between our DBAs and Server Builders and I am interested in what others are doing. Our DBAs want to take the default SQL install into the C: drive, making sure that NO logs are written to C:. That way there is no chance for the C: drive to become full, crashing the box. Server guys are insisting that we install to a drive other than C:.

I would appreciate any discussion re: what others consider best practice , industry standard, if such a things esist.

Thanks.

Install On D Drive

Is there a way to install SQL 2005 Express on a different drive? The server that I want to use has 700MB availible on the C drive and 80 GB availible on the D drive. can I install SQL and all tools on the D drive?

MSDE: Can I Install Onto My D: Drive?

When I ran the install for MSDE, it installed the DB server and the databases onto my C: drive and under program files...

The instructions I followed were listed here:

http://www.asp.net/msde/default.aspx?tabindex=0&tabid=1

I'd like to be able to install it to my D: drive. I've looked through all of the docs but I can't find any information on how to change the install path. Would anyone know how to do this?



Thanks,

LD.....

New NT/SQL Install, Drive Partitioning

We have purchased a new Server at my company. We previously had two servers. One was the NT file server and then we had another SQL Server. Well, we've bought one box to replace both old boxes. I have 3 18.2 GB SCSI drives running on a RAID-5 configuration. I've partitioned the C: drive as 2GB and it will only be used for NT files and NT Utility apps.

On the old system I had all my data files on one physical drive and all of my logs on a seperate physical drive. Now, with RAID, the three drives act like one big 36GB drive. Finally, my question...

How should I partition this drive? Should I put the SQL Server App, my data files and my logs all on one partition? Should they each have their own partition? Should it be a mix (App & Log, Data & Log, etc.). Also, how much space do I need just for the application if I put it in its own partition?

I've never installed SQL Server before, so if anyone has any other suggestions, tips, tricks, etc., I'd love to hear it. Either post here or e-mail me responses.

Thank you all very much
Merry Christmas!

Install Error - Not Enough Space On Drive C

Hello Everyone,

I wasn't able to find the answer to my question by searching the forum. I would very much appreciate if anyone would help me.

I need to install the SQL Server Workgroup trial. I wasn't able to find the workgroup trial so I was trying to install the enterprise instead. (If anyone knows how to get ahold of the workgroup trial that would be a help too)

I keep getting the following error when running the SQLEval.exe:

There is not enough space on drive C: to extract this package

I did an internet search on this error and it seems there is a bug that requires the amount of free space not be a multiple of 4. I currently have 13.2 GB free space and I have tried adding and removing files, to no avail. I have tried downloading the file in a few different versions in case the file was corrupted, and rebooting etc, but still I keep getting the same message. I only have one drive!!!

Can anyone help me with this?

Why The Upgraded Files On Drive C Instead Of D

I just upgraded SQL6.5 standard(Installed 7.0 and ran Wizard to upgrade dbs) to SQL7.0 by running the exe file.

It turned out that the MSSQL7 folder is follen on Drive C instead of Drive D which is what I wanted. When I was running the upgrade exe file, there was no prompt to ask me the right path.

How could I have the MSSQL7 folder installed on D drive?

Thank you for help

Drive Letters And MDF/LDF Files...

All,

I'm writing to ask if anyone knows whether or not MS SQL server stores in any system tables the association between a database and the drive letter/directory path where its corresponding MDF/LDF files are located.

Thanks,

Isaac

Need To Move Data And Log Files To A Different Drive?

Data Files In Flash Drive

Hi friends, i want to know something abt sql server installation and database properties as under.1) how much disk space reqd by multiuser sqlserver 2000 db to install ?2) is it possible to install sql 2K on Flash Drive ( gen connect at USB) ?3) When v create a database user Enterprise Manager , which files created by database ?4) If i Know datafiles name of a database e.g. pubs , and if v copied on cd and paste on other system which has sql 2K install , does those database works ?5) is it possible to create database on flash drive ? thanx in advance.

Moving DB Files To Another Drive On The Server.

Howdy 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!

SQL 2012 :: Fusion-IO Drive And MDB Files

We have a cluster with two nodes and two instances of SQL Server 2012 Standard Edition running on them. Volume W: is a Fusion-IO card.

On one of these nodes a lot of database names are showing up in the resource monitor as *.mdf files (W:0MSSQL1…).

How and why SQL Server is using these files? They only show up on one of the nodes having more load.

Volume I: is the volume where the transaction log is written so we can explain these files.

TempDB Files On Root Of Drive

Documentation that supports the placement of Tempdb files on the root of a drive, i.e T: instead of T: empdb. I am positive this is not a best practice, but when challenged could not find any documentation that would support that view.

How To Move Only The Transaction Log Files (.ldf) To A Different Drive?

Hello guys and girls. I have installed SQL Server 2005 Standard Edition and I have specified that the databases should be created on the K: drive. This is okay but now I need to move all the transaction log files (.ldf) to the L: drive. I have already changed the default location for the log files to point to the L: drive and the new databases that were created after the installation have their transaction log file correctly in the L: drive but now I need to move transaction log files for the master, model, temp ... databases. How can this be done? And are there any gotchas?

Space Problem On SQL Server Install Drive (was Question???)

On the drive that SQL server is install on which is the C drive the amount of space is 495mb, can the amount of space be a potential problem, I am so used to looking at the drives that contains the data and log files and the backup.

So My question is should I also concern myself with the drive the sql server itself is installed on?

Thanks

Lystra

Drive Filling Up / Moving Data Files?

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.

Recovery :: Point New Log Shipping Files To Different Drive

I have two databases on a Production Server that I want to Log Ship to a Test Server.  According to the sys.master files the physical File Location is on an E drive. Early attempts at Log Shipping these two files error'd out due to space issues on the E drive (one Log Shipped and then one err'd out).  I was subsequently informed from the server group that they would prefer that I Log Ship these two database files over to the M Drive where more space is available.  In fact, they modified the Server Properties / Database Settings / Database Default Locations (for Data and Log) to the larger M drive (I'm not really sure why they just don't increase the E drive space but there is proabably a good reason).

Okay, so now my problems have been solved.  Easy enough.  Now I deleted the successful Log Shipped database and started from scratch.  However, as before, one db restored and one failed (due to space issues).  Apparently, both db are pointing towards the E drive.  How is that possible? 

So here I am with one successful database and the normal sys databases pointing to the E drive.  What is the best way of approaching this  move to the larger and preferred M drive?

Reading/writing Files To Network Drive

We have a package that is using a ForEach loop container to access files on a network drive. For some reason I am getting a message that the ForEach enumerator is empty and did not find any files that matched the pattern. For the pattern I left the default *.* for testing purposes. I have specified the file folder as \remoteserverfilesharesubfolder and also as \remoteserverc$filesharesubfolder and have gotten the same message. However when I map a network drive and set the file folder to the network drive it finds the files. Is this a permissions issue?

After I finish processing the file I want to move it to a new directory. Once this is deployed in production, the package will not be running under a domain account and probably won't have access to the network folder. Is there any way to specifiy in the connection manager itself that it should use a specific account to access the folder?



TIA,

Sabrina

Move Distribution Data/log Files To Another Drive

I haven't found the definitive answer on how or if this can be done without removing replication. I'm thinking ALTER DATABASE modify_file is the way to go. Anybody know if this will work or a better way to go about it?

Thanks

Transaction Log File Corruption When Database Files Are Placed In SSD Drive

The MDF and LDF files are placed in SSD drive and tempdb files are placed in HDD drive. Snapshot isolation is enabled on the database. When a script is executed to insert data with NULL value to a table which has NOT NULL column, the transaction fails and then a log undo happens which fails and takes the database to suspect mode.

But when the MDF and LDF files are placed in HDD drive all this do not happen. The transaction just fails.

DB Design :: Clear Space On The Drive - Shrinking Log Files

I have a database which has log file size 300 GB. As the drive is filling up i need to clear the space on the drive, for that i have to shrink the log file. 

Unfortunately i dont have option to take backup of the database.And i am not able to shrink the file now. Is there any way to shrink the log file with out taking backup of it ?

Hard Drive Crashed. Master && User Db Mdf && Ldf Files Lost

Hello.

One of our hard drives has crashed and as a result we have lost our master mdf/ldf & user db mdf/ldf files. It's not that a critical system by any means, but if the hard drive crashes and the master mdf/ldf files & user db mdf/ldf are lost, is there any way of restoring the system?

I'm thinking we probably need to re-install Enterprise Manager completely, and re-install the user db from a backup.

Any advice/suggestions would be much appreciated.

Thanks in advance,

Recovery :: Access To Files On Shared Drive When Cluster Is Shut Down?

Is there a way to get access to the files on the shared drive from either of the nodes when the SQL Cluster is shut down?

It doesn't look like there is, but hoping there is some trick. I see how it can be done with a Windows Cluster but not a SQL Cluster.

Sql 2005 Script Force To Start MergeSychronization

HI every One,

i m new on this site, acutall i have design a pull subscribtion with merge replication, and sychronization start about every 3 hours time, acutally some time my boss need to start replication immediatly, to replicate data between two server,

is there any script code that i will run to start the sychronization immediatly ?