<div>
Disconnecting SQL database files from SQL Server while SQL Service is running can be disastruous and yous SAN or disk aray should never do that. Can you see the databases you mentioned above listed in SQL SSMS on that SQL server? What status are they in? RECOVERY? 
</div>


<div>
You may be lucky and in this case you should be able to bring it back ONLINE. If some transactions are lost....you may incure some data lose but frist try to run following command against mster db in that SQL box:<br />
<br />
ALTER DATABASE database_name SET ONLINE;<br />
GO <br />
<br />
<br />
If the command above runs clean you MUST issue a DBCC CHECKDB immediately after that like:<br />
<br />
DBCC CHECKDB (database_name) WITH NO_INFOMSGS;<br />
GO<br />
<br />

</div>


<div>
The first command runned correctly but the second one gave these error<br />
<br />
Msg 945, Level 14, State 2, Line 1<br />
Database 'PFC_IMG_ARCH' cannot be opened due to inaccessible files or insufficient memory or disk space. &nbsp;See the SQL Server errorlog for details.<br />

</div>


<div>
Do you have enough disk space where ALL SQL database files are? I mean all physical locations for system db's and user db's<br />
<br />
is there anything else in SLQ logs - via SSMS, Management section SQL Server Logs
</div>


<div>
Yes I have disk space available 7.6gb.<br />
<br />
In the log file:<br />
<br />
Date &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;10/5/2011 2:12:19 PM<br />
Log &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;SQL Server (Current - 10/5/2011 2:12:00 PM)<br />
<br />
Source &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;spid27s<br />
<br />
Message<br />
Starting up database 'PFC_IMG_ARCH'.<br />

</div>


<div>
lcohan has you on the right track. I will only throw in that I have seen instances with network connectivity issues with disk is that sometimes the operating system does not recognize the volume is back online until after a reboot. Or if it is seeing the volume, SQL may not be recognizing the path is back online (i.e., accessible), so you can try restarting the SQL services to see if it picks it up. Have not tried the latter as in the past when these kinds of things happened with SANs, a reboot is usually followed on servers connected. Having redundant paths is expensive, but as stated it is disastrous if this is consistent as you are potentially removing disk in the middle of I/O operations.
</div>


<div>
HI mwvisa1, after a restart in the sql services it recognizes the dbs, but take sometime to put them online again.<br />

</div>


<div>
That is true and based on &quot;mwvisa1&quot;'s comment can you &quot;see&quot; the files from inside SQL? I mean if you would run a command like below against that drive leter:\folder what do you get? Even though - a restart for SQL service at least might be required.<br />
<br />
exec xp_cmdshell 'dir G:\SQL_Data_files_folder\*<wbr />.*'<br />

</div>


<div>
I made a restart of the sql services and now all the dbs are running.<br />
<br />
But to avoid the future issues like that what you guys recommend?
</div>


<div>
&quot;<b>Having redundant paths</b> is expensive, but as stated it is disastrous if this is consistent as you are potentially removing disk in the middle of I/O operations.&quot; Alternatively or in addition, find the root cause of when these drops occur. Maybe there is some configuration, firmware, etc. that needs to be looked at with Network Engineers.
</div>


<div>
Your SQL files MUST be on a physical location (SAN, ARRAY, local disks, etc) ALLWAYS connected to the SQL server computer WHILE SQL Server Service is running. <br />
This is it - you can't disconnect db files from SQL while this service is running.
</div>


<div>
Exactly. To make my comment more clear, if you cannot get rid of instances where a particular ISCSI switch disconnects for a short period of time -- I think in the past even millisecond lapses cause issues, then you will need to have dual switches/paths to your SAN or disk array. That way the OS and SQL do not suffer a disconnect because of one failing. Knowing WHEN and WHY the disconnects are happening may help to determine the risk of BOTH paths going offline at the same time by ensuring the proper portion of route is made independent. In other words, if the root cause is power, having the switches on the same PDU does you know good. Likewise, if it is the switch, having dual connections in the same switch does you no good. Hopefully that makes more sense as I see I did not give enough details before.
</div>


<div>
Besides all the above, I don't want to sound out of tune however....<br />
<br />
&quot;Yes I have disk space available 7.6gb.&quot; <br />
<br />
for a SQL server hosting multiple databases seems extremely little today...I would put immediately alerts to let me know if the disk(s) system(s) hosting SQL DB files is runing on less than 20% free disk space.<br />
That is - a bad query with some cartesian product can fill very quick the 7.6GB available in the log file.
</div>


<div>
I agree. I have one application written very poorly that fills 30gb during one transaction. It may even go higher if that was not all we had left since we have not migrated to new hardware yet. Very annoying.
</div>


<div>
The 7.6 gb free is on the C drive... I have all the dbs in the secondary partition and there I have at least 60gb of free space.
</div>


<div>
Good deal, so then you just need to focus on keeping the data storage attached. Good luck!
</div>


<div>
what is the best way of backups when you have a database of 150gb?
</div>


<div>
<div class="content wysiwyg-content">
Hi, I have a blade server where I have runing on it more than 15 databases.<br />
Because of the disk space I was forced to put some of the big databases in a storage Synology and it is connected using the Microsoft ISCSI Iniatiator.<br />
My problem is: the connection of the server to the storage is connected trough a Cisco Switch because I cant connect the blade server directly conected to the storage because of a configuration on the network cards of the chassis of the blade servers.<br />
The problem that I have is that sometimes the connection is disconnected and I have to put back the connection online and have to go to the sql and take offline and online the databases, but now I have 3 databases that when I want to put the database ofline it says that the databases are not accessible.<br />
What can I do to put the dbs online?<br />
<br />
Thanks<br />
Joel
</div>
</div>


Hi, I have a blade server where I have runing on it more than 15 databases.
Because of the disk space I was forced to put some of the big databases in a storage Synology and it is connected using the Microsoft ISCSI Iniatiator.
My problem is: the connection of the server to the storage is connected trough a Cisco Switch because I cant connect the blade server directly conected to the storage because of a configuration on the network cards of the chassis of the blade servers.
The problem that I have is that sometimes the connection is disconnected and I have to put back the connection online and have to go to the sql and take offline and online the databases, but now I have 3 databases that when I want to put the database ofline it says that the databases are not accessible.
What can I do to put the dbs online?

Thanks
Joel

sql databases 2008

Windows Server 2008 and Windows Server 2008 R2, based on the Microsoft Vista codebase, is the last 32-bit server operating system released by Microsoft. It has a number of versions, including including Foundation, Standard, Enterprise, Datacenter, Web, HPC Server, Itanium and Storage; new features included server core installation and Hyper-V.

Windows Server 2008

Microsoft SQL Server is a suite of relational database management system (RDBMS) products providing multi-user database access functionality.SQL Server is available in multiple versions, typically identified by release year, and versions are subdivided into editions to distinguish between product functionality. Component services include integration (SSIS), reporting (SSRS), analysis (SSAS), data quality, master data, T-SQL and performance tuning.