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.
| Author |
Topic |
|
wardsan
Starting Member
48 Posts |
 Posted - 2004-07-14 : 09:17:30
|
| Folks,what are the advantages of placing text/image fields in a different filegroup? I have an app that stores images of bills in a sql server db. Unfortunately ,when the tables were created, the image field data went into the primary filegroup by default. Now, the primary filegroup is huge. I am reading that there is no way of changing the filegroup for the image data.Can anybody shed any light? |
|
|
AndrewMurphy
Master Smack Fu Yak Hacker
2916 Posts |
Posted - 2004-07-14 : 09:28:01
|
| move the images out of SQL would be an even better solution....and just store the path to the image in SQL....the performance/data management issues surrounding images isn't worth the hassle of putting them into SQL.....search here for similar advice already given by others. |
 |
|
|
wardsan
Starting Member
48 Posts |
Posted - 2004-07-14 : 09:54:45
|
| This is not an option |
|
|
|
derrickleggett
Pointy Haired Yak DBA
4184 Posts |
Posted - 2004-07-14 : 13:44:53
|
| You would need to:1. Rename the tables.2. Create the old table names and relationships as tables on a new filegroup.3. Move the images.4. Delete the tables you renamed.It would be even better to redesign the tables so you have small tables with only images and an index. You can put them on a filegroup by themselves.MeanOldDBAderrickleggett@hotmail.comWhen life gives you a lemon, fire the DBA. |
|
|
|
wardsan
Starting Member
48 Posts |
Posted - 2004-07-26 : 07:00:57
|
| Folks,can I get someone's advice on how best to separate to data, indexes and image/text fields? Should they all be in separate filegroups? So, filegroup for primary, data, index, text/image.... |
|
|
|
Kristen
Test
22859 Posts |
Posted - 2004-07-26 : 09:02:15
|
| I think I would be keen to get them out of other tables - so have an IMAGES table with just ID and IMAGE and then have other tables point to them; but sounds like the App is already build, so may not be possible to do this.Prevents people who use SELECT * getting a truck-load of data they didn't expect, and also tidies up some problems with transport layer wanting TEXT/IMAGE to be the last column, and various other gotchas - many of them seem to be redudant with current ADO versions, but-you-never-know!Sorry, doesn't answer your specific question as I don't know enough to have an informed view.Kristen |
|
|
|
wardsan
Starting Member
48 Posts |
Posted - 2004-07-26 : 09:32:07
|
| I'm afraid this a bought in app so we have no control over how the tables are defined.... |
|
|
|
Kristen
Test
22859 Posts |
Posted - 2004-07-26 : 09:59:31
|
| I thought that might be the case ...Can't they restructure the database to something more manageable for you then? Sounds like it ought to be their problem - my clients always make that sort of thing my problem :(Kristen |
|
|
|
|
|
|
|
|
text/image fields