Question about Intel SS4000-E (SS4000ENA)

1 Answer

Can´t use INTEL SS4000-E to host the files of my database from SQL SERVER 2000

How can I use INTEL SS4000-E to keep the files of my Database in SQL SERVER 2000 running from a Small Business?

Nothing seems to work!

Posted by on


1 Answer

  • Level 3:

    An expert who has achieved level 3 by getting 1000 points


    An expert that got 10 achievements.


    An expert that got 5 achievements.


    An expert who has achieved Level 3.

  • Master
  • 409 Answers

The SS4000-E  is a NAS storage server.  To the best of my knowledge it is not possible to put database files on a NAS.  They need to do on Direct Attached Storage.

Posted on Oct 22, 2008


1 Suggested Answer

  • 2 Answers

SOURCE: I have freestanding Series 8 dishwasher. Lately during the filling cycle water hammer is occurring. How can this be resolved

A 6ya expert can help you resolve that issue over the phone in a minute or two.
Best thing about this new service is that you are never placed on hold and get to talk to real repairmen in the US.
The service is completely free and covers almost anything you can think of (from cars to computers, handyman, and even drones).
click here to download the app (for users in the US for now) and get all the help you need.
Good luck!

Posted on Jan 02, 2017


Add Your Answer

Uploading: 0%


Complete. Click "Add" to insert your video. Add



Related Questions:

3 Answers

Repair database without being attached SQL 2005

Use SQL Server Repair Kit. A convenient, reliable and ultimately efficient MS SQL database repair tool for system administrators, developers and database experts. Best in class performance and outstanding usability for users with and without experience.

Read more:

May 13, 2015 | Microsoft SQL Server 2005 Enterprise...

4 Answers

Recover data from corrupt .mdf and .ldf files.

You can find more information here:

Open your SQL Server Management Studio console. This application shortcut is available in the SQL Server directory in the Windows Start button.
· Enter the system administrator user name and password. SQL Server's administrator user name is "sa." This account is required for privileges to restore the database. If your restoring on a host provider server, use the administrator user name and password they supplied for your account.
·Right-click your database name and select "Attach." In the new window that opens, click the "Add" button to open a dialog box.
·Select your MDF file and press the "Ok" button. It may take several minutes to restore the database if it is a large file. Once the process is finished, browse your tables to verify the data. The database is now restored.
If nothing helped try to use:SQL Server Fix Toolbox

Nov 28, 2014 | Microsoft SQL Server 2000 Standard Edition...

2 Answers

Creating a new database using an MDF file

An MDF file isn't a backup file isn't the main data file (or master data file depending on who you ask) hence the file extension MDF. You can attach the MDF to the database by right clicking on the databases folder in Enterprise Manager (SQL 2000) or Management Studio (SQL 2005) then selecting all tasks and then Attach Database.
When you do this you will get an error about the log file missing. This shouldn't matter as SQL Server will simply create a new log file for you.
This will only work if the SQL Server was stopped when you copied the MDF file from the old SQL Server. If you copied the file while the SQL Server was running this file probably will not attach either and you will need to get a valid backup of the database.
Download help tool for sql database - SQL Server Restore Toolbox.
You can read up more on SQL Server here.

Nov 16, 2014 | Microsoft SQL Server 2000 Standard Edition...

7 Answers

How to recover SQL server mdf files?

RecoveryFix for SQL database recovery software is recover and repair MDF files components from corrupted SQL server database. This software compatible with Windows 7, Server 2008, Vista, Server 2003, XP and 2000. More details see this site: or download this tool from

May 06, 2014 | Microsoft Database Software A5K-02817 SQL...

5 Answers

How to recover deleted Microsoft SQL server MDF files?

Recover and repair MDF files with simple and efficetive tool to repair and recover MDF files from corrupt and damaged SQL server, which tool support all king of SQL server version and Windows OS. Visit here:
Read blog post: Corrupt MDF File Repair Utility

Apr 17, 2014 | Computers & Internet

5 Answers


Perform following steps to recover sql server database:
  • Create a database with same size that you are trying to recover
  • Shutdown the SQL server
  • Swap old mdf file with new mdf file
  • Start the SQL server
  • Database may go in suspect
  • Set database in emergency mode
  • Run DBCC CHECKDB with repair_allow_data_loss to repair database

USE [master]

It may result some data loss. If you don't want to lose any single data then use 3rd party SQL repair software from Stellar Phoenix.

Mar 19, 2008 | Computers & Internet

4 Answers

Restoring files from the database

I suggest you use the Enterprise manager (gui tool to manage SQL).
Restoring a single table is not an option.
You can however restore a file or filegroup.
Make sure to backup before you start and NOT to restore database to its original name or original file location, to avoid acidents.
Normally you will have databases with only 2 files: the data at its Primary file group, and log file.
You may wish to create a new file group and move tables to the new group by recreating them there and exporting data from old table to new table. Then recreate indexes. This may prove to be complex as all tables and indexes have unique names and can't coexist with exact duplicate of them.

oh yea..... did I say backup?
well just in case backup backup backup backup backup backup backup backup backup backup backup backup backup backup backup backup backup backup backup backup backup backup backup
but dont overwrite that backup

Feb 11, 2008 | Microsoft SQL Server 2000 Standard Edition...

Not finding what you are looking for?

Open Questions:

0 Answers

Greetings, I've been using the Intel Entry Storage System SS4000-E as a simple backup network drive for the last few years. It showed up as Drive Z: on all of my Windows machines and I just copied other drives/folders onto it as needed. It's far from the full capability of this device but it's suited my purposes. Recently, I decided to upgrade the drives and increase the total storage space from 2 TB (4 500 GB drives, Raid 0) to 6 TB (4 1.5 TB drives). The software doesn't allow me to make one 6 TB drive, so I made three (X:, Y:, and Z:), with sizes ranging from 1.49 TB to 1.99 TB, accessible as \storage\public3, \storage\public2, and \storage\public1 respectively. I also created the required shared folders using the minimum (200 MB) for both so I could have as much room as possible for large shared partitions. I also took the opportunity to upgrade the firmware to version 1.4, build 709, since I was installing new drives. I backed up some data to the Z: drive (\storage\public1) and filled about 1.5 TB. Then I started copying folders from another system to Y: drive (around 900 GB in all). Everything seemed to be going well until I looked in on the copy after around 800 GB had transferred. Files were being copied *extremely* slowly, like 100 MB in 10 minutes! I aborted the transfer and ran a test to eliminate network issues as the problem. I tried copying a 100 MB file from Y: drive to Y: drive. It took around 10 minutes, as above. I tried the same thing on Z: drive and it was almost instant. Something was somehow causing that part of the network drive to move at a snail's pace. I then accessed the management screen via a browser and got a message saying that one or more drives had either failed or been changed (Disk Change Notification - raid_disks_changedF.cgi). Two tables that show all four disks - serial numbers and capacities - are shown, one table being previous configuration and the second being current configuration. Both tables are completely identical. Clicking on "Scan" or "Continue" resulted in the same message, so I clicked on "shut down" and tried to access the network drive after it rebooted. I had no problem getting into the Z: drive part of it but both X: and Y: weren't being seen at all anymore. I'm aware of the fragility of a Raid 0 and wonder if it could be so easily disrupted during a large transfer such that I face the possibility of initializing all four drives and starting over. I'm at a loss as to what could be going wrong here or how to fix it. I really just want a simple means of copying lots of data over from various networked machines without any additional software. This system worked fine before. What could have happened? Thanks for any help. Bob

Apr 13, 2011 | Intel SS4000-E (SS4000ENA)

See all Intel SS4000-E (SS4000ENA) Questions

Intel SS4000-E (SS4000ENA) Logo

Related Topics:

293 people viewed this question

Ask a Question

Usually answered in minutes!

Top Intel Computers & Internet Experts


Level 3 Expert

2600 Answers

Alun Cox

Level 3 Expert

2678 Answers


Level 3 Expert

781 Answers

Are you an Intel Computer and Internet Expert? Answer questions, earn points and help others

Answer questions

Manuals & User Guides