DB Engine :: Database Default Location Is Not Showing System Drive
Oct 30, 2015In SQL Server 2012 Instance properties ,database default location is not showing system drive E: which was my backup drive. How can I add it again?
View 8 Replies
ADVERTISEMENT
DB Engine :: System Database Files Location
May 16, 2015I have C,D,E drives on server. Data files will be on D and Log on E. My question is what is best practice for data and log files for system databases during sql server installation selection? Should they be on C drive along with SQL Server installation or D & E? If they should not be on C then what is the reason and what is benefit to move them on other drives.
View 9 Replies View RelatedPost SP2-Hotfixes Fails To Install Database Services On Clustered Servers With System Dbs On Non-default Location
Jan 9, 2008Hi,
We've had this issue for awhile, but I have not been able to find a resolution for this. We have 2 identical servers (hardware & software) set-up: IBM x3850-(88633RU) running Windows Server 2003 Enterprise x64 (5.2.3790 SP1 Build 3790 R2). Server A was running SP1 (Build 9.0.2047) on a 3-node active-passive-passive failover cluster. Server B was running SP2 + Hotfix KB933097 (Build 9.0.3152) on a 2-node active-passive failover cluster. Both these servers are heavily utilized, and when originally installed with these versions of SQL Server Enterprise 2005 experienced no issues during or post-install. The original install of SQL 2005 Enterprise on both these servers had the Cluster Group Selection "Data files" setting changed to "M:MICROSOFT SQL SERVER" so that all system dbs and binaries would be installed to that location. On Server B where SP2 had already been applied, the update was downloaded on May 1, 2007, well after the GDR issues which had been plaguing SP2 releases was supposed to have been resolved.
Our problems began the night when we tried to apply hotfix KB933097 on Server A, and cumulative update packages 1,2,3 on Servers A & B, as well as catch-up the same SP2 and hotfix packages on other non-clustered servers where default system db locations remained the same. On all servers other than Servers A and B, the installs proceeded smoothly and without issue.
On Server B, which was already running SP2 + Hotfix KB933097, we tried installing Cumulative Update Package 1 (Build 9.0.3161) on the primary node. The install proceeded until the following errors were encountered:
"[Microsoft][SQL Native Client][SQL Server]Cannot find the object 'dm_exec_query_resource_semaphores', because it does not exist or you do not have permission."
"[Microsoft][SQL Native Client][SQL Server]Cannot find the object 'dm_exec_query_memory_grants', because it does not exist or you do not have permission."
After this, the setup finished with the message "Product: Microsoft SQL Server 2005 (64-bit) - Update 'Hotfix 3161 for SQL Server Database Services 2005 (64-bit) ENU (KB935356)' could not be installed. Error code 1603. Additional information is available in the log file C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixSQL9_Hotfix_KB935356_sqlrun_sql.msp.log."
We rebooted the server and tried several times to reinstall the hotfix as sa and as the database service account with full windows and sa credentials, each time with no success, and rebooting between retries. All other components were installed successfully. We were hesitant to try uninstalling the hotfix, since it was unable to be removed successfully in previous attempts. However, when I connected to Database Engine using Management Studio, I found that the version of SQL being reported was in fact Build 9.0.3161! Everything also appeared to be running properly.
I tried to to Google the answer, but could only find information as applied to SP1 when system dbs master and mssqlsystemresource were located on different locations (http://support.microsoft.com/default.aspx?scid=kb;EN-US;918695 ). I had already verified that all system dbs, including the ones mentioned, were originally and currently located together on M:Microsoft SQL ServerMSSQL.1MSSQLData.
Finally I contacted a fellow DBA who advised me to continue installing all the other hotfixes, and then compare all SQL files against other servers where the install succeeded to ensure all system files were updated correctly (matching file sizes and datetime stamps). Since we were depending on a fix in Cumulative Update Package 3 to fix a critical log-shipping security issue, I went ahead with the rest of the installs, getting the same error with each package, rebooting between each install.
We found after the final install that the mssqlsystemresource files in the M:Microsoft SQL ServerMSSQL.1MSSQLData
directory were in fact updated after each install with a new timestamp, and that all files in C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn matched on both file size and timestamp. The log-shipping security issue we were looking to fix also appeared to be resolved by the last update.
On Server A, which was running SP1 (Build 9.0.2047), we installed the same SP2 package as we had on Server B with no issue. We rebooted and then tried to apply the same Hotfix KB933097 (Build 9.0.3152) that had been applied successfully on Server B and found to our surprise that the same errors were being generated here as well. We continued to apply the rest of the hotfixes so that both servers matched software updates. Comparing the above directories showed that files seemed to have been updated, even though database services appeared to be not installed.
It looks like we now need Cumulative Update 5 hotfix package in order to deal with WMI alerting issues, but I'm afraid to apply it until we have a known resolution for the past errors.
Since this issue was supposed to be resolved by SP2, I'm not sure why these post-SP2 hotfixes should fail. It seems to me to be an issue of the directory location of the system files which is in question.
I can post the hotfix log files as well, if anyone is interested in seeing them.
Any help would be greatly appreciated. As well, does anyone have any idea when SP3 is scheduled to come out? I really don't like applying hotfixes which are usually untested for general purposes, and it seems Microsoft is delaying this in favour of releasing SQL 2008.
SQL Server Admin 2014 :: Installing System Databases To A Non Default Drive?
Mar 25, 2015How can you install the System Databases to a drive other than the default?
I want the Data Files to be installed on D:MSSQLData and the log files to be stored on D:MSSQLLog.
For better, quicker answers on T-SQL questions, click on the following...
[URL]
For better answers on performance questions, click on the following...
[URL]
SQL 2012 :: Log Shipping - Secondary Database Path Showing Wrong Location?
Mar 17, 2014I've configured log shipping to use for DR purposes. I'm concerned that the physical location of the secondary is mis-reported by SQL Server Management Studio.
Viewing the secondary location (with Studio DB_name Properties Files) shows the path of the primary DB (I expected it to show the path of the secondary).
This SQL command shows the correct/actual paths of both primary and secondary DB's when run on their host servers.
SELECT name, physical_name AS CurrentLocation, state_desc FROM sys.master_files
Is this just cosmetic?
Here is an Example of how the Studio shows the incorrect path for the secondary.
Example:
(Primary) servername=prodSrv, DBname=aquaDB, Actual_Path=G:aquaDB, SQL-studio-Properties-Path=G:AquaDB, sys.master_files Path=G:AquaDB,
Log shipped to
(Secondary / Read Only) servername=DRSrv, DBname=aquaDB, Actual Path=F:aquaDR, SQL-studio-Properties-Path=G:AquaDB(WRONG), sys.master_files Path=F:aquaDR
DB Engine :: Insufficient System Memory In Resource Pool Default To Run Query
Jul 7, 2015My Integrity job started failing recently with the following error. Msg 701, Level 17, State 123, Line 1 There is insufficient system memory in resource pool 'default' to run this query. Process Exit Code 1. The step failed.
select @@ version
Microsoft SQL Server 2008 R2 (SP2) - 10.50.4033.0 (X64)
Jul 9 2014 16:04:25
Copyright (c) Microsoft Corporation
Developer Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) (Hypervisor)
System is having 4GB RAM and SQL is using most of it. It has 2 processors.
Where Is Database Default Location?
Sep 27, 2007Hey,
I'm trying to get the information where the databases are stored by default.
With Management Studio I can look on Server Properties -> Database Settings -> Database Default locations
Is there a way to read this information in TSQL?
Cheers,
Manolo
Changing The Default Location Of A New Database
Oct 16, 2006If you enter "Create Database test", the database files (mdf file & log file) are created, by default, in:-
C:Program FilesMicrosoft SQL ServerMSSQLData
I want to change that to:-
D:Database Files
I sucessfully moved the model database to this location (using the instructions in BOL) assuming that all new databases would now get created in the same location, but they don't. They still get created in:
C:Program FilesMicrosoft SQL ServerMSSQLData
So how do I change the default?
(It's not satisfactory to have to move each database after it's created)
Thanks, Andy Abel
DB Engine :: Copy Database File To Different Drive?
Jun 7, 2015I have to perform disk maintenance on current drive - Drive 'D' where it has sql data (mdf file) and I have added new drive - Drive 'E' By the way Drive 'C' have the program files for SQL Server 2008 R2 What is the correct process to transfer sql data (mdf file) from Drive 'D' to Drive 'E' and later remove Drive 'D' from the server.
View 12 Replies View RelatedChanging Default Database Creation Location....
Aug 7, 2002I have installed my modell database onto c:mssql7data...
How do I now change the properties of this so that when someone creates a database, the path it will get created to is set to d:
I thought that I could just move model, but it seems that this isn't possible.
Any advice?
thanks
derek
SQL Server 2005 Default Database Location
Oct 13, 2007
Hi,
I would like to change the default location where new databases are created.
In Server Management Studio, I right clicked my instance and selected Properties. I selected the Database Settings option and am presented with an option to change the Database Default Location (the location for databases and logs can be changed here). If I change the paths for the DB's and logs, and create a new DB, the new files are saved to the new default location paths that I just entered.
My question is this:
If I change these paths, will my system databases (master, model, msdb, tempdb) still be accessible and usable by SQL server? I don't need (want) to change the location of these files, only all my other databases and logs.
Will this do what I want?
Thanks for the help!
Oliver
Digram Showing Schema Of System Database Table
Dec 1, 2000Does anyone know where I can get a digram showing the database schemas for all of the system database. I need to know the realtionship between tables in the system databases. Would like to download something from the internet preferably, or if someone has something they can e-mail?
View 1 Replies View RelatedDatabase Mail Attachments Filling Up The System Drive!
Apr 30, 2007Hi all,
Has anyone run into this issue before?
My company uses database mail extensively for alerting and the like, and most emails sent have attachments. We've put in place procedures for removing emails older than a month from the MSDB database, however we've now had a client server completely run out of the disk space due to attachments being stored in the C:Documents and SettingsUserLocal SettingsTemp folder!?!
When I check the sysmail_delete_mailitems_sp sproc, it only removes entries in the MSDB tables, and doesn't remove these temporary files in the temp directory.
Does anyone know why SQL Server stores them in the temp directory of the service account user, as well as how we can remove them (apart from manually deleting the files), as we need to have an automated process for cleaning up emails, and at the moment SQL Server 2005 doesn't handle this very well.
I've checked this on our test server as well, and we're getting the same there, and this server is running the latest SP2 + hot fixes.
Thanks,
Reece.
SQL Security :: Server Won't Start After Mistyped System Database Names When Moving Them To New Location
Apr 24, 2015I'm using SQL Server 2012 and was attempting to move the msdb, model, and tempdb databases to a new location and accidentally gave their log files an mdf extension instead of ldf when providing the new pathfilename. After the server wouldn't start I checked my script and noticed my error. I have good backups of my system databases, so I was hoping to start the MSSQLSERVER service in single-user mode (using the -m startup parameter) and then just restore master using sqlcmd.
Unfortunately the service was starting but I couldn't connect via sqlcmd using any of the three protocols (it said the server was not found or not accessible each time). I also tried using the dedicated Admin connection but I got the same error. Then I went into the Templates folder and copied the master, msdb, model, and tempdb templates into the DATA folder and tried to restart SQL Server but still no luck (now the MSSQLSERVER service won't start at all). Is there an easy way to fix this mess without having to reinstall from the setup application?
Where's My Default Sql Server Database Engine?
Jul 11, 2007I am a novice in DB learning.
A few months ago, I installed the ms sql server 2005, and use it to learn the book SQL Server 2005 for dummies. It worked just fine. But after i finished the book, i uninstalled the program and deleted the express database engine. Perhaps it was an incomplete installation, yesterday when i tried to reinstall the sql server 2005, i found some configuration tools still in the directory. So i used windows to remove those tools. After that, i reinstall the sql server 2005, and changed some values in the register. The reinstallation goes well. But after it was done. I started the management studio, there's no default database engine for me to connect! All I could find in Internet is how to connect to a database engine without information about how to create one. Can anyone tell me why and help me out?
i am a novice.
SQL Server Admin 2014 :: Changing Drive Letter For System Database And User Databases
Oct 18, 2013I 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 RelatedMoving The Location Of A DB To Another Drive
Feb 22, 2008I 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?
New Cluster Drive Not Showing Up
Oct 3, 2007I've added a new drive to a clustered instance of sql 2000. Go to the node the instance is active on, the drive shows up. But...try to add a backup device that lives on the new drive (which was, after all, the whole point of the exercise) and SQL Server is blind to that drive. I have vague recollections of it recognizing the clustered drives when i set up all this a couple years ago. Could it be that it recognizes all the drives it'll ever recognize at the moment of installation? Anybody know?
thanks,
Garth
:beer:
:D :D :D
:beer:
Moving The Location Of By Datafiles From One Drive To Another
Feb 9, 2007Hey 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.
Installation Requirements - Drive Location?
Apr 17, 2007I was trying to install the Developer Edition of 2005 last night, and ran into a strange issue. I specified F:SQLDev as the installation directory, but the installer still refused to install claiming lack of disk space. Checking the disk cost, I saw that it was still asking for about 1.5 GB on my C: drive. I double checked, and I did specify the installation directory as F:SQLDev.
Is there documentation somewhere that describes why it would require space on the boot drive? Or am I missing a switch somewhere or something?
Thanks in advance for any help.
Backing Up To A Non-local Drive/location
Dec 19, 2007I've been working with SQL Server for a few years now and I've had quite a few cases where users cannot backup SQL to a network location or external hard drive. Why can SQL not do this? Is it some limitation of the speeds at which SQL needs to backup the information and the external hard drives/network drives do not meet the requirements?
DB Engine :: How To Change Error Log Location
Nov 30, 2006I have been trying to change the location of the SQL 2005 error log. It's logging to the default location at
C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLLOG
I want to move the log location to the E drive because it can get quite large. I already changed the setting in the SQL Server Error and Usage config tool, but this did not seem to make a difference.
Default Db Location
Feb 17, 2000Hi,
currently, the default location for new db is c:msqldbdata and I want to change it to another location.
anyone know how?
Thanks.
DB Engine :: Migrating Clustered Server From One Location To Another
Oct 16, 2015We currently have two virtual machines running on Windows Server 2003 together with SQL 2005. These servers are in a cluster and are using multiple physcial RAW disk mappings from shared storage (SAN) for their shared disks within a VMware ESXi 5.1 cluster.I need migrate these SQL servers over to new infrastructure, in a new physical location. I tried using VMware converter to import the active member server in the SQL cluster, but I am receiving VSS errors when running the conversion. I can see that shadow copy is disabled on all the disks on the server.
View 3 Replies View RelatedDefault Save Location
Jul 10, 2007How can i change the default folder to which my database files are saved? right now it's saving everything to
program filesmssql servermssql.1mssqldata
uggg! i can't even find an option to use a "save as" or export the mdf file. the "save as" tries to save the solution file. Any help is greatly appreciated.
Default Backup Location
Aug 18, 2006Hi
I am almost ashamed to ask but I cannot find the setting
Is there a way to set the default backup location in sql 2005? I dont want to change the folder every time I specify a new media.
Thanks
Alex
DB Engine :: How To Change Location Of Secondary Data File
Nov 9, 2015I added a secondary data file to TEMPdb yesterday and gave it a wrong location by mistake. If I try to change the location, then I am getting an error now. I think that is because TEMPdb is in use and that is why I cant change it's secondary file's location. Do I need to take TempDB offline and then change the secondary file's location??
View 3 Replies View RelatedSystem DB's Location
Oct 2, 2007I have an installation of SQL2005 SP1 configured as follows:
Dell Poweredge 2650 with 4 GB RAM
c:, d: and e: are all on the local host and f: and g: drives are on a SAN. I have the system db's on the e: local disk and the Team Foundation Server databases and logfiles on the SAN disks. SQL2005 is installed to the E: disk.
We are migrating VSS to TFS and our times are very long for a simple 1 GB migration.
I need to know if I need the application databases and logfiles and system databases on the same disk because I see a lot of disk thrash and the tempdb is getting large, 3 GB today.
SQL architecture - should the system db's be on the same disk as the application db's?
Thanks
Default Location For Transaction Logs
Feb 19, 2002I'm setting up a new server and would like the default location for the transaction logs to be on a different drive from the databases. Seems like the best way to do this would be to configure the Master database log location for the drive & directory where I want all trans logs stored. So far, I've been unable to accomplish this. I know I can specify the log location manually each time I create a database, but I'm hoping to configure a default. Is this possible to configure? And if so, how?
Environment is W2k with SQL7.
TIA, Sara
Default Backup File Location
Dec 28, 2004Hi
I want to change the default backup location of MSSQL. I know we can configure it while installing. But I want to change the default backup location of a particular database, running on a database server.
The default location is like.
Program FilesMicrosoft SQL ServerMssqlBackup
Thanks in advance,
Prasanna.
Change Default Location Where New DB's Are Created
Jul 19, 2007Hello
The default location where db's are created is almost full.
Is there any way to change the default location where the .mdf and .ldf are created when I create a new db? I know I can do this when I create a new db and go select where I want it to be, but can I make it default to a different directory automatically so no human intervention is needed?
tia
r/P
DB Engine :: Keeping Service Up While Taking Drive Offline
Sep 2, 2015I have clustered instance with two (2) data drives on it. Drive J has around 50 databases on it and drive K has about 15. One of the system administrators was trying to increase the size on K by 20 GB and he instead increased it by 200. Now he needs to take the accidental 180 GB back but the drive will need to come offline briefly. Is it possible to take the K drive offline, along with the databases whose data files resides on it, without taking the whole instance down?
View 7 Replies View RelatedProblem To Install SSIS To Different Location Then Default
Oct 15, 2006I have only SQL engine installed to my D drive. (SQL Server 2005 no SP1)
I want to install SSIS to my D drive but i can not.
It only gives me the option to install to the default drive C:...
saying that "the sql shared path has already been configured"
Is this a BUG ?
No Tools nor Notification Services are installed (which i understood to be related to the same path as SSIS)
thanks,
raviv