AnsweredAssumed Answered

Adding SW data to server

Question asked by Michi Speck on Mar 4, 2009
Latest reply on Mar 13, 2009 by Michi Speck

Like • Show 0 Likes0
Comment • 4

Hi

Does any see any problems with adding all SW data, ie sld material database, texture images, Toll box etc onto a server machine so all information is keep in one place, and hence elminate having different databases on each computer on the network?

I am assuming this will give the benefit that when new materials or images for textures are added they will be available to everyone on the network.

Cheerio

Michi

Michi Speck Mar 13, 2009 1:39 AM

Correct Answer

Thanks for your in puts, we have decided to add our common data, including the tool box to our server. When we work on a project for a client we keep all the project files locally, hence we have just decided to use the toolbox to quickley generate fasteners etc and then save them off locally. This way all files in a project are kept together.

Thanks again

Michi

See the reply in context

No one else had this question

Outcomes

Jeff Mirisola Mar 4, 2009 9:48 PM

Actually, what you're describing is common practice for multi-user environments.

Actions

Anna Wood Mar 5, 2009 12:52 AM

To add to what Jeff says, SW has the ability to path to those server locations in the System Option > File Locations.

All your company standard items should be on the network and everyone's system set to pull from the company standards.

Cheers,

Actions

William Peacock Mar 7, 2009 11:34 AM

For the ToolBox:
Depending on the number of users at your location and whether you use configurations or parts, this may be opening you up for headaches due to network lag. We had our SW set up the way that you describe and changed to local. We are using configurations and some of the files we use commonly are 20+MB. This does not sound like a large file but even with a 1GB network we gained 10 minutes opening a 2000 part assembly drawing by switching to local. We have 12 users.

I agree with the rest and we do that now.

Actions

Michi Speck @ William Peacock on Mar 13, 2009 1:39 AM

Actions

4 Replies

Jeff Mirisola Mar 4, 2009 9:48 PM
Mark Correct
Correct Answer
Actually, what you're describing is common practice for multi-user environments.
Like • Show 0 Likes0
Actions
Anna Wood Mar 5, 2009 12:52 AM
Mark Correct
Correct Answer
To add to what Jeff says, SW has the ability to path to those server locations in the System Option > File Locations.

All your company standard items should be on the network and everyone's system set to pull from the company standards.

Cheers,
Like • Show 0 Likes0
Actions
William Peacock Mar 7, 2009 11:34 AM
Mark Correct
Correct Answer
For the ToolBox:
Depending on the number of users at your location and whether you use configurations or parts, this may be opening you up for headaches due to network lag. We had our SW set up the way that you describe and changed to local. We are using configurations and some of the files we use commonly are 20+MB. This does not sound like a large file but even with a 1GB network we gained 10 minutes opening a 2000 part assembly drawing by switching to local. We have 12 users.

I agree with the rest and we do that now.
Like • Show 0 Likes0
Actions
- Michi Speck @ William Peacock on Mar 13, 2009 1:39 AM
  Unmark Correct
  Correct Answer
  Thanks for your in puts, we have decided to add our common data, including the tool box to our server. When we work on a project for a client we keep all the project files locally, hence we have just decided to use the toolbox to quickley generate fasteners etc and then save them off locally. This way all files in a project are kept together.
  
  Thanks again
  
  Michi
  Like • Show 0 Likes0
  Actions

Adding SW data to server

Outcomes

Related Content

Recommended Content