[dbworks] remote disk database

[cacciatorino]

I would like to realize this architecture (for reasons of mobility and backup that I am not explaining for brevity'), considering having dbworks that turns on ms-sql serrver:

1) Remote disk database files on smb sharing hosted on linux machine

2) database engine, dbworks client and swx that instead turn on workstation

Is that possible? Obviously I should start the sql engine as a user, ie after login in windows since this s.o. connects network units only after login, but it's a bearable nuisance when compared to the benefits that would give me for my particular use.

 

[re_solidworks]

I would like to realize this architecture (for reasons of mobility and backup that I am not explaining for brevity'), considering having dbworks that turns on ms-sql serrver:

1) Remote disk database files on smb sharing hosted on linux machine

2) database engine, dbworks client and swx that instead turn on workstation

Is that possible? Obviously I should start the sql engine as a user, ie after login in windows since this s.o. connects network units only after login, but it's a bearable nuisance when compared to the benefits that would give me for my particular use.

Hi.

I don't know dbworks and I can't tell you if it works. what I can assure you is that linux environments with swx should be avoided as they are not certified by the swx.
the native files of solidworks you have to keep them on a machine with windows, regarding the pdm I don't know.

 

[flfn]

Hello, personally I ospito the sw files on a condivione in debian smb, and I did not detect any problem.

to say that you have to configure it, especially read/write permissions

greetings

 

[cacciatorino]

Hi.

I don't know dbworks and I can't tell you if it works. what I can assure you is that linux environments with swx should be avoided as they are not certified by the swx.
the native files of solidworks you have to keep them on a machine with windows, regarding the pdm I don't know.

That's why I didn't hear mechworks, I'm gonna try to hear what they say.

However, my server is linux and solidworks works very well. as to the lack of certification of a file-server running linux, I think it is only a commercial agreement with microsoft or simply lack of willingness to do tests.

 

[re_solidworks]

Hello, personally I ospito the sw files on a condivione in debian smb, and I did not detect any problem.

to say that you have to configure it, especially read/write permissions

greetings

That's why I didn't hear mechworks, I'm gonna try to hear what they say.

However, my server is linux and solidworks works very well. as to the lack of certification of a file-server running linux, I think it is only a commercial agreement with microsoft or simply lack of willingness to do tests.

Hi.

I have a nas netgear readynas pro business, I would say it is a good product made good for use up to 100 users.
I recently had a problem opening a large set (a plant) where swx told me that there are too many open files.
after the call to assistance it turns out that it is a problem known in the mixed networks windows/linux
at the moment the problem has arisen only in this case and the aid is really huge, but it seems there is no solution (at least from technical support).
I do not know linux, but in the case of the nas I think it is "blind" by the producer and almost untouchable.
I basically expect to replace it with a nas equipped with windows 2008 file server edition.
If the number of components remains reasonable there is no problem.
returning to my problem I tried to search on the net but in the kb of the microsoft we talk about win nt, 95, 98, not 7 or xp, so the problem is old and no longer treated.

 

[cacciatorino]

after the call to assistance it turns out that it is a problem known in the mixed networks windows/linux

Is it possible that this is a problem due to the 32bit server operating system?

 

[SolidUser]

what I can assure you is that linux environments with swx should be avoided as they are not certified by the swx.
the native files of solidworks you have to keep them on a machine with windows, regarding the pdm I don't know.

solidworks is a filesystem-agnostic.
solidworks also works with fat and fat32.
clearly, along with the ntfs extensions, become the most common and used.

if the pc with windows installed connects to the samba server, then solidworks will be able to read and write on it.
However, solidworks does not know or does not take into account whether it is reading or writing from a sharing or local disc.

said this, not all nas are created equal to not all samba daemons turn equally.
this is due to the fact that nas manufacturers use diferent linux packages or solutions.
also from the hardware used.
see synology and qnap.

often and willingly problems that arise in the use of networked files, disappear if you work locally.
almost the totality of solidworks pdms make checekd-out locally and therefore the 'read and save' is much less critical.

There are too many variables in using networked files:
- reliability of the network
- ability to support a constant and challenging flow of i/o
- management of lost packages on the network
- the same compatibility between client and server

then solidworks does not say that it does not support nas with above linux, it just says that you need to be careful about the written above.

 

[SolidUser]

please move the topic here. ?