Building a server

[pstylesss]

Here is the response to the email I sent our rep.

The SQL database contains all of the DVMS information (users, car configs, etc.) and video file data (file name, meta data, etc.) The video files themselves are storage in the internal hard disk storage array contained in the server quoted. SQL queries the storage array based on the search criteria entered by the officer and contained in the SQL data base. The server is a ?file? server to a point, however, it is only for the in car video solution. No other applications will be running on this server.

The server does not do any encoding, decoding or encryption. The encoding and decoding of the videos are handled by the in car unit. The MD5 Digital signature is created for the video at the time of recording by the in car system.

The upload workstation is used to upload video, check out hard drives or allow the officers to search for and export needed videos. No encoding, decoding or encryption is performed at this level.

The SQL database is typically loaded to the same drive as the OS or another partition on that drive. The SQL server IS on the same server that the internal storage resides in.

I would recommend between 60G ~ 80G for the C partition drive. Because we will load the DVMS (Digital Video Management System) software which will have administrator system logs. The logs may be expended in future depending on the number of officers which your department may add in future. So, we would highly suggest having at least 60G preferably but of course is up to your department.

How large would one, twelve hour video be?
It depends on the Mpeg formats.

Mpeg 1 (VCD quality) = .6G per hour
Mpeg 2 (DVD quality) = 1.2G per hour

If we base on the highest resolution which is Mpeg 2 it will be about 10G for 12 hours of video.