Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2000 Forums
 SQL Server Development (2000)
 Populating Tables and Finding Excel XP Bridge

Author  Topic 

AskSQLTeam
Ask SQLTeam Question

0 Posts

Posted - 2002-05-07 : 11:03:09
Joshua writes "Hello,

I am brand new to all of this technology (I'm a static web guy), so, I'm going to ask a bone head question. I have created a table successfully and I want to populate it with some baseball stats and a picture of a player representing each stat (For test purposes). How do I do this. Do I use insert? If so, I have already tried this and it is not recognizing any of my commands or tables. Is there a graphical interface I can use to input data. What about the jpgs? I swear I've looked around in the manual and in Ray Rankin's 1400 page Book and nothing is painted clearly for me. I don't receive any help here at the company, yet they tell me they want this technology.

I have composed all of this info in a nice Excel sheet, but there is no Excel XP bridge in the import list. Where can I get this driver?

Stuck,
Josh"

robvolk
Most Valuable Yak

15732 Posts

Posted - 2002-05-07 : 12:36:16
You can import from Excel into SQL Server using Data Transformation Services (DTS). DTS is very well documented in Books Online, and you can find examples here on SQL Team:

http://www.sqlteam.com/SearchResults.asp?SearchTerms=dts
http://www.sqlteam.com/FilterTopics.asp?TopicID=109

And also on this site:

http://www.sqldts.com

The images are going to be tricky. You can store image data in a SQL Server table, but you are STRENUOUSLY ADVISED NOT TO. This link has info on how to do it:

http://www.sqlteam.com/item.asp?ItemID=986

You should instead store images as regular JPEG or GIF files on the hard drive, perhaps in their own special folder, and then store a link to that image file for each player's record. There is NO benefit to storing image data in the database, especially if you need to modify the image. All it does is add extra steps to an already multiple-step process.

This may change in the future with the new version of SQL Server (Yukon) but until then, if you want to avoid a lot of aggravation, store the images as separate files and create a column that stores the path and filename of those images in your database.

Go to Top of Page
   

- Advertisement -