I'm trying to set up a replication of SQL 2005. I have 2 servers running and I like to configure it that the second server takes over the SQL database when the first server fails. The database files are located at a ISCS network drive that can have only 1 initiator. We tried to set up a cluster server, but that seems not possible because of the 32 bit proccesors inside the servers. We have installed windows server 2003 EE on both servers. Is there a way that the second server can take over the connection to the ISCS from the first server??
Hello all, I have Microsoft iSCSI Initiator (SAN) installed on a SQL Server machine and has this drive acting as a local drive. All the database's data files are residing on this drive, attached with SAN. It runs as a service "Microsoft iSCSI Initiator" on the SQL Server machine.
Now the question is, when we restart the SQL Server all the databases change their status to "Suspect" and we have to stop all the sqlserver services (all the SQL instances) and start them all up. This is the only temporary solution we came up with. Could any one has any real solution or had encounter such a problem before?
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$])
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.
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
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?
How to backup half of dbs from a server on C drive and the other half on D drive and vice versa, first half on D drive and other half On C drive using only one job and one stored procedure??
Using scheduling from job add 2 schedules to the job so first schedule backup first half to C and second half to D , the second schedule backup first half to D and second half to D.
I am installing the X86 Executable version of SQL Server. I copied it to my desktop and clicked RUN. It extracts the files and then the Install Wizard tells me there is not enough space on the C Drive to load the program. I have 23 gigabits of free space and the program only takes about 900 megabits.
Hi 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.
I have a shared drive mapped to the h: drive letter on my sql server and I want to create new databases on that drive. Is this at all possible? I try it and I couldn't see h: even if I typed it in.
What problems will I get if the hard drive for the transaction logs becomes defective? Will this affect transactions and/or backup? What should I do to fix this problem?
In reading material on the quorum drive on a sql server cluster in mentions this is the drive the logs are written to. Is this referring to sql log files that are dumped by a process or scheduled job, or some other log files?
I have an MSDE installation on Windows server 2003. It looks like the C: drive is taking the brunt of the data when I load up the database. I would like to specify a different drive for data...Is there a way to do this?
I know this isn't exactly SQL help, but I alwasy get great help here and thought someone might know why I'm having problems. I'm trying to map to a drive where I have a SQLExpress database on another computer within a workgroup. This is the cmd line I'm using...
NET USE * \XPPRO1SQLExpress /USER:Admin /SAVECRED /PERSISTENT: YES
I'm thinking the problem is with the * (which names the new drive with the next available letter), or that I have to use a password. Everything I've found says nothing about specifying a password though.
The error message I get says "A command was used with conflicting switches."
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!)
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.
Any comments, please. I have a new server 5x160GB drives. It needs to run IIS for a web app and SQL Server 2005. One user database. I was thinking of dividing space as follows and wanted to get some thoughts from others.
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 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?
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?
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?
I have and issue with a query, I tried every thing but I couldn't find why. Here is the issue, I have one big DB1 with about 30 tables, the query based on a join of 5 tables, I have the right index in place, when I run the query it will take about a minute and 20 sec. But I have another DB2 on the same server and I imported just the 5 tables form DB1 with the same index, when I run the same query it will take 6 seconds.
I did drop and recreate the indexes and drop and recreate the statistics but still the same thing no difference.
I'm running SQL7 SP3.
Do you have any idea what might be the issue here?
hi, I have NT server which has drive c: 500 MB and drive d has 44 GB.
I know that the person who set up this server did not give enough space to the c drive, here is the problem. I am running sql server 7.0 which has 30 GB of data in the d drive. I need to reconfigure the NT hard drive so I can allocate 2 GB for C drive and 42 GB for D drive.
What is the best, safe method to accomplish this task.
