December 11, 2008 at 1:13 pm
We need to implement an application that stores recorded videos (metadata) into a database. Should this be on SQL 2000 or 2005. As this is for internal purpose, I dont think we need to go with this on production. Any suggestions??
Thanks in advance!!
The_SQL_DBA
MCTS
"Quality is never an accident; it is always the result of high intention, sincere effort, intelligent direction and skillful execution; it represents the wise choice of many alternatives."
December 15, 2008 at 7:54 am
Are you saying you want to actually store the video's within the database or just the path?
I'd suggest 2005, or if you really want to store the video in the DB look into 2008.
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
December 15, 2008 at 8:22 am
SQL 2000 is dead
SQL 2005 is dying (almost)
SQL 2008 is just born
Go for 2008
Wilfred
The best things in life are the simple things
December 15, 2008 at 11:29 am
Well, we have decided not to put the actual video into the database, as we want to have control over the amount of data that actually goes into the database. We will store the url's in the database and point it to the app server. I am also of the view that SQL 2005 be used for this. I wasn't aware of the features that SQL 2008 has to achieve this, but will do a little research on it..Thanks again!!
The_SQL_DBA
MCTS
"Quality is never an accident; it is always the result of high intention, sincere effort, intelligent direction and skillful execution; it represents the wise choice of many alternatives."
December 15, 2008 at 12:10 pm
The_SQL_DBA (12/15/2008)
Well, we have decided not to put the actual video into the database, as we want to have control over the amount of data that actually goes into the database. We will store the url's in the database and point it to the app server. I am also of the view that SQL 2005 be used for this. I wasn't aware of the features that SQL 2008 has to achieve this, but will do a little research on it..Thanks again!!
In SQL2008 FILESTREAM may or may not be useful for you but you should look into it 😉
* Noel
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply