I'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?
Hello SQLServer gurus, We created the database with transaction log files and datafiles on the same drive. Now we want to change the transaction log file location to a different drive. Please let me know the steps to follow. THanks...
How 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.
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
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
If 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)
Hello 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
I 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.
Prior to SP2, when you clicked the save button it would take you to the root of Report Server. With SP2 (in old-style Report Manager mode, not Sharepoint integrated mode) it takes you to the /Models directory by default when you click save. Is there a way around this?
If I launch Report Builder via the following URL, it does fix the problem. But it doesn't let me pick table/matrix/chart. I would like to override the default save location AND be able to let the user pick table/matrix/chart:
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.
I have just installed SQL Server 2005. I was not given a choice during installation (that I remember seeing anyway) about which drive I wanted to place the default SQL instance on.
It ended up on C: and I needed it on D:.
So my questions are:
Is there a way to move it to D: that is easier than the way you had to go about it in SQL 2000? Is there a way to do it during setup so I can avoid this in the future?
What is best practise for what this number should be?
I have seen guidance saying set to a number greater than 25000, but not from any source I particularly know or trust. (I checked SANS, NIST-CIS and the NSA, but I couldn't find anything.
version:SQL Server 2000. db size: 25.6GB trans log file: 32GB so far: I have read the Forum FAQ on "clearing the transaction file" and some DBCC SHRINK in Books Online.
I am trying to set up maintenance plan or backup plan. File sizes are getting very large and performance is horrible since we have had no regular maintainence in the past (No DBA in house).
1. What is the best way to identify the location of the transaction log file associated with a particular database?
When I right-click on the database name in Enterprise Manager and select properties, I can see one location for the transaction log.
However, If I right-click on the database > All Tasks > Shrink Database > click Files and select Temp_Table_Log, I get a different location.
2. We delete then repopulate about 105000 records in one particular table each day. In addition, we do the same with about a hundred rows in several other tables daily. -- Should I be doing Full Backups nightly? -- I have the option set to "AutoShrink" on the db. Will this truncate and shrink the transaction log as well as shrink the db when I do a full backup?
What is the best way to clear the transaction logs. My backup job each night is ending because it says it is running out of disk space and I need to clear up the transaction logs. Any help is appreciated. I see many different options (trucate option, auto shrink, etc.), just need some assistance tosome more specific best approaches. Thanks
Im having issues truncating my transaction logs. I have logs in excess of 40 gigs. All the info in the BOL is very vague. Any assistance would be apreciated.
to take the transaction log back up regularly I should have truncate log on check point false. If I do so then how will I truncate the log. regards, Renu
I am trying to import records via bcp (about 1,500,000 records) and I keep running out of disk space. Is there any way to limit or do away with the transaction log (and still be able to import)?
When I look at the Database maintience plan history entry for backup I have a message that reads: "Backup can not be performed on this database. This sub task is ignored".
Have anyone come across this error before?? As part of the Maintenance plan some transaction log are being backup and some aren't instead they receive the message above.
i have several sql servers doing maintenance plans and backing up the transaction logs to tape. unfortunately it seems that the server keeps adding the transaction logs to the same tape, without overwriting them. Nowadays a transaction log backup to disk takes 2 minutes but when done to tape it is taking up 1hr54minutes. What can i do so that the tape is automatically initialised without having to do it manually... Thanks
Is there a way to view the transactions from a .TRN transaction log file? If so can I overwrite some of the transactions on the file and then restore from it? I am just curious.
Hi, I know just about nothing about SQL Server. I am getting this error:The log file for database 'my_database' is full. Back up the transaction logfor the database to free up some log space.I can't access the transaction logs to back them up. I am told that my ISP'stech support should have it set up to shrink those logs automatically everyso often. Is that true?Why are they needed? Up till Monday, the logs are just of our getting SQLServer set up, so couldn't the logs just be deleted? Most of my site can'trun with this problem.I'd appreciate any enlightenment anyone can give me!Thanks, Jill
