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
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
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.
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!
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.
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.
View 7 Replies View RelatedHello 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?
View 11 Replies View RelatedI 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.
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.
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?
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
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
Hi,
View 12 Replies View RelatedThe 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.
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 ?
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,
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.
Hi
I have been trying to use openrowset with a shared drive, and even though the share has "full control" permissions granted to "everyone" and the accout that SQL runs under has been granted explicit full control permissions I am unable to open the file which itself has no security on it.
Can I not use a \ path and only use mapped drives?
Thanks
below works...
SELECT * FROM OPENROWSET('Microsoft.Jet.OLEDB.4.0','Excel 8.0;Database=C:5People.xls', [Sheet1$])
below doesn't work...
SELECT * FROM OPENROWSET('Microsoft.Jet.OLEDB.4.0','Excel 8.0;Database=\cluster02FileManager5People.xls', [Sheet1$])
We just upgraded SQL 6.5 to 7.0 --database was imported (thinking
all table structure/ data all were imported.)
Software application lost its login connection.
How can I re-establish the connection ?
Thanks for your help !!
Lewis
Hi all
We recently upgraded from sql 2000 to sql server 2005. Our system was developed using Microsoft visual Basic.
Since we upgraded to sql server 2005 our system has been very slow. I suspect that it was because of the new sql 2005 installation that i made.
Does anyone know how to solve this problem for me to be able to increase the perfomance speeed of our system again.
It has been stressing me for a while now.
Pliz help
Thanks!
My SSMS does not seem to be upgraded after SP2:
Microsoft SQL Server Management Studio 9.00.1399.00
Microsoft Analysis Services Client Tools 2005.090.1399.00
Microsoft Data Access Components (MDAC) 2000.085.1117.00 (xpsp_sp2_rtm.040803-2158)
Microsoft MSXML 2.6 3.0 4.0 5.0 6.0
Microsoft Internet Explorer 6.0.2900.2180
Microsoft .NET Framework 2.0.50727.832
Operating System 5.1.2600
My coworkers have a higher version 9.00.34xx or something.
I am trying to generate scripts w/ the "drop before create" function...
Thanks
I am trying to move a log file from one drive to another.
What I have done is add another file to my file group. So now my log has a file on the 'e' drive and one on the 'f' drive. I now want to remove the file on the 'e' drive. I have emptied the file on the 'e' drive. When doing the command:
ALTER DATABASE Uniprodruntime
REMOVE FILE m_rk_runtime_log
I get the following error message..
Server: Msg 5020, Level 16, State 1, Line 1
The primary data or log file cannot be removed from a database.
I have also gone into enterprise manager and tried to delete the file and it does nothing.
Has anyone run into this?
How do you compare SAN drive vs local drive on a 32 bit server?
Is it good idea to move my DB files to a SAN instead of local?
Canada DBA
Server: SQL 2008 R2
1: TempDB keeps getting filled. Restart of the server has not fixed it. I shrink it, but the space gets filled again. Now I can't even shrink it anymore
2: TempDB is at the wrong location. Its current location is this :C:Program FilesMicrosoft SQL ServerMSSQL10_50.SQLPROD6MSSQLDATA empdb
How do I change its location?
C:Program FilesMicrosoft SQL ServerMSSQL10_50.SQLPROD6MSSQLDATA empdb
Correct location of TempDB should be: TempDB(T:) But its not there
Hi,
I did a same server upgrade from SQL 6.5 to 7.0 about a month ago. I never deleted the old 6.5 installation/databases. Yesterday, for some reason SQL 7.0 wouldn't start. When I looked at SQL 6.5 enterprise manager, it showed that 6.5 was started. So I stopped it. I tried to start 7.0 back up and it would just start 6.5. I tried a reboot... that didn't work. Then I uninstalled 6.5, rebooted, and SQL 7.0 finally came up. I check the error logs and it showed that there was a "short stack dump" (details below)
Would a "stack dump" have caused sql to revert back to 6.5?
Thanks,
LC
Dump thread - spid = 10, PSS = 0x3505b4b4, EC = 0x3505b664
Stack Dump being sent to e:MSSQL7logSQL00003.dmp
************************************************** *****************************
*
* BEGIN STACK DUMP:
* 03/13/00 15:07:33 spid 10
*
* Input Buffer 66 bytes -
* SELECT category FROM z_guarantees WHERE z_guarantees.code ='GGTD'
*
************************************************** *****************************
-------------------------------------------------------------------------------
Short Stack Dump
0x77f67a2b Module(ntdll+7a2b) (ZwGetContextThread+b)
0x0077fc6b Module(sqlservr+37fc6b) (utassert_fail+1a0)
0x005b0ebe Module(sqlservr+1b0ebe) (XCB::Rollback+4a)
0x005aa843 Module(sqlservr+1aa843) (bds_defect_xact+84)
0x0051abea Module(sqlservr+11abea) (clean_process+200)
0x005b22fd Module(sqlservr+1b22fd) (language_exec+5f9)
0x4106135c Module(opends60+135c) (execute_event+659)
0x4106164b Module(opends60+164b) (process_commands+f3)
0x4109285a Module(ums+285a) (ProcessWorkRequests+ed)
0x41092d28 Module(ums+2d28) (ThreadStartRoutine+139)
0x7800bee4 Module(MSVCRT+bee4) (beginthread+ce)
0x77f04ee8 Module(KERNEL32+4ee8) (lstrcmpiW+be)
2000-03-13 15:07:34.09 spid10 CImageHelper::GetSym Error - The specified module could not be found.
0x00000000 Module(sqlservr+ffc00000)
2000-03-13 15:07:34.16 kernel SQL Server Assertion: File: <xcbmgr.cpp>, line=1299
Failed Assertion = 'pss->IsXcbLocked ()'.
Dump thread - spid = 10, PSS = 0x3505b4b4, EC = 0x3505b664
Stack Dump being sent to e:MSSQL7logSQL00004.dmp
************************************************** *****************************
*
* BEGIN STACK DUMP:
* 03/13/00 15:07:34 spid 10
*
* Input Buffer 66 bytes -
* SELECT category FROM z_guarantees WHERE z_guarantees.code ='GGTD'
*
************************************************** *****************************
-------------------------------------------------------------------------------
Short Stack Dump
0x77f67a2b Module(ntdll+7a2b) (ZwGetContextThread+b)
0x005b5af3 Module(sqlservr+1b5af3) (ex_raise2+35c)
0x00506417 Module(sqlservr+106417) (ex_raise+5f)
0x0077fbfe Module(sqlservr+37fbfe) (utassert_fail+37e)
0x005b0ebe Module(sqlservr+1b0ebe) (XCB::Rollback+4a)
0x005aa843 Module(sqlservr+1aa843) (bds_defect_xact+84)
0x0051abea Module(sqlservr+11abea) (clean_process+200)
0x005b22fd Module(sqlservr+1b22fd) (language_exec+5f9)
0x4106135c Module(opends60+135c) (execute_event+659)
0x4106164b Module(opends60+164b) (process_commands+f3)
0x4109285a Module(ums+285a) (ProcessWorkRequests+ed)
0x41092d28 Module(ums+2d28) (ThreadStartRoutine+139)
0x7800bee4 Module(MSVCRT+bee4) (beginthread+ce)
0x77f04ee8 Module(KERNEL32+4ee8) (lstrcmpiW+be)
2000-03-13 15:07:34.22 spid10 CImageHelper::GetSym Error - The specified module could not be found.
0x00000000 Module(sqlservr+ffc00000)
2000-03-13 15:07:34.44 spid1 Closing file e:mssql7datarain.mdf.
2000-03-13 15:07:34.83 spid1 Closing file e:mssql7datarainlog.ldf.
Dump thread - spid = 8, PSS = 0x2110b4b4, EC = 0x2110b664
Stack Dump being sent to e:MSSQL7logSQL00005.dmp
************************************************** *****************************
*
* BEGIN STACK DUMP:
* 03/13/00 15:07:34 spid 8
*
* Input Buffer 62 bytes -
* select interface from z_property where ( property ='DALMAN' )
*
************************************************** *****************************
-------------------------------------------------------------------------------
Short Stack Dump
0x77f67a2b Module(ntdll+7a2b) (ZwGetContextThread+b)
0x0077fc6b Module(sqlservr+37fc6b) (utassert_fail+1a0)
0x005b0ebe Module(sqlservr+1b0ebe) (XCB::Rollback+4a)
0x005aa843 Module(sqlservr+1aa843) (bds_defect_xact+84)
0x0051abea Module(sqlservr+11abea) (clean_process+200)
0x005b22fd Module(sqlservr+1b22fd) (language_exec+5f9)
0x4106135c Module(opends60+135c) (execute_event+659)
0x4106164b Module(opends60+164b) (process_commands+f3)
0x4109285a Module(ums+285a) (ProcessWorkRequests+ed)
0x41092d28 Module(ums+2d28) (ThreadStartRoutine+139)
0x7800bee4 Module(MSVCRT+bee4) (beginthread+ce)
0x77f04ee8 Module(KERNEL32+4ee8) (lstrcmpiW+be)
2000-03-13 15:07:34.92 spid8 CImageHelper::GetSym Error - The specified module could not be found.
0x00000000 Module(sqlservr+ffc00000)
2000-03-13 15:07:35.00 kernel SQL Server Assertion: File: <xcbmgr.cpp>, line=1299
Failed Assertion = 'pss->IsXcbLocked ()'.
2000-03-13 15:07:35.06 spid8 Using 'sqlimage.dll' version '4.0.5'
I am beginning to write stored procedures for an application which is to be written in VB5. The stored procedures will be written in 6.5 but when the system goes live, we hope to upgrade to SQL server 7
What I want to know is what changes will I have to make to the stored procedures when I upgrade to 7.0?
Hi
While a database upgrade schema changes were being made the Mirror became disconnected will this recover itself when it reconnects or will it be the case that we will have to copy the db files to the Mirror and set it up from scratch.
It was set up as a synchronise mirror
I just did a 2005 "In-Place" upgrade to a 2000 server yesterday, and now we're getting intermittant time-out errors trying to connect via SQL Server Management Studio. Sometimes we connect instantly, then if I try again 10 minutes later, it might time-out. No problems with our other 4 SQL 2005 servers (2 were just upgraded, 2 are native 2005). No timeouts so far when logged on to the server directly, just when logging in from our desks.
It's set to TCPIP only (removed named pipes), but can't think what else might be the problem. Any ideas ?
One little thing I just noticed while comparing to another server: In the console, a "good" server has the little green arrow on the server & SQL Agent icons, while the "problem" server is connected, but there is no green arrow. If I log on the server directly and open SQL, I get the green arrows. Is that trying to tell me something about the connection ??
Server Error in '/' Application.
Database 'C:INETPUBDEMO.TRUTHSTONE.COMAPP_DATAASPNETDB.MDF' cannot be upgraded because it is read-only or has read-only files. Make the database or files writeable, and rerun recovery.Cannot open user default database. Login failed.Login failed for user 'NT AUTHORITYNETWORK SERVICE'.
Hi,
Strange one. I have copied my working web-site to the production server and get this message.
Tried copying new set of database files and reset the server to ensure no applications could be accessing the database files. Still get the same error.
Works fine on my Visual Studio VWD Express version.
Mitch
PS I am not trying to upgrade the database, just use it!
Dear all,
I am trying to save a newly created diagram in SQL Server 2005 SP1.
The error message is:
----Beginning of pasted error message---
===================================
Cannot insert the value NULL into column 'diagram_id', table 'adt_db.dbo.sysdiagrams'; column does not allow nulls. INSERT fails.
The statement has been terminated.
The 'sp_creatediagram' procedure attempted to return a status of NULL, which is not allowed. A status of 0 will be returned instead. (.Net SqlClient Data Provider)
------------------------------
Program Location:
at Microsoft.VisualStudio.DataTools.Interop.IDTDocTool.Save(Object dsRef, String path, Boolean okToOverwrite)
at Microsoft.SqlServer.Management.UI.VSIntegration.Editors.DatabaseDesignerNode.Save(VSSAVEFLAGS dwSave, String strSilentSaveAsName, IVsUIShell pIVsUIShell, IntPtr punkDocDataIntPtr, String& strMkDocumentNew, Int32& pfCanceled)
----End of pasted error message---
The database I use has been upgraded from SQL Server 2000.
I am running in SQL Server 2000 Compatibility Mode (80) but changing the compatibility mode to SQL Server 2050 (90) does not make any difference with regards to this error.
Being 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
DELETED ORIGINAL LOAD AND TRIED TO REINSTALL. CANNOT START LOCAL SERVER
View 1 Replies View Related