To Cable, or Not to Cable
-
@scottalanmiller said in To Cable, or Not to Cable:
@dbeato said in To Cable, or Not to Cable:
The only thing I would not run over wifi is VoIP phones, not because of security but stability on the network.
I'd be hesitant to do SAN or database connections over Wifi, too
Yeah, sorry I missed that
-
@dbeato said in To Cable, or Not to Cable:
@scottalanmiller said in To Cable, or Not to Cable:
@dbeato said in To Cable, or Not to Cable:
The only thing I would not run over wifi is VoIP phones, not because of security but stability on the network.
I'd be hesitant to do SAN or database connections over Wifi, too
Yeah, sorry I missed that
LOL, there are lots of infrastructure things I'd not do on wifi. But the original article was pretty much written from an "all IT is the end user" perspective as if there was no tech involved anyway.
-
@scottalanmiller said in To Cable, or Not to Cable:
@dbeato said in To Cable, or Not to Cable:
The only thing I would not run over wifi is VoIP phones, not because of security but stability on the network.
I'd be hesitant to do SAN or database connections over Wifi, too
There's some new wireless about that I wouldn't be afraid to use as interconnects with servers, but it's not wifi. mm wave beamforming and 40Gb/s if I remember right.
-
@scottalanmiller said in To Cable, or Not to Cable:
@dbeato said in To Cable, or Not to Cable:
The only thing I would not run over wifi is VoIP phones, not because of security but stability on the network.
I'd be hesitant to do SAN or database connections over Wifi, too
Can't speak to SAN over WiFi, but databases over Wifi will suck big time -- even if your wifi is reliable.
-
@eddiejennings said in To Cable, or Not to Cable:
|can|———string———|can|
I win security!
*snip, hides scissors*
-
@dafyre said in To Cable, or Not to Cable:
@scottalanmiller said in To Cable, or Not to Cable:
@dbeato said in To Cable, or Not to Cable:
The only thing I would not run over wifi is VoIP phones, not because of security but stability on the network.
I'd be hesitant to do SAN or database connections over Wifi, too
Can't speak to SAN over WiFi, but databases over Wifi will suck big time -- even if your wifi is reliable.
SAN is even worse.
-
@dafyre said in To Cable, or Not to Cable:
@eddiejennings said in To Cable, or Not to Cable:
|can|———string———|can|
I win security!
*snip, hides scissors*
Curses! Foiled by the script kiddie who googled
how to compromise a yarn-based connection.
</silliness>
-
@dafyre said in To Cable, or Not to Cable:
@scottalanmiller said in To Cable, or Not to Cable:
@dbeato said in To Cable, or Not to Cable:
The only thing I would not run over wifi is VoIP phones, not because of security but stability on the network.
I'd be hesitant to do SAN or database connections over Wifi, too
Can't speak to SAN over WiFi, but databases over Wifi will suck big time -- even if your wifi is reliable.
We have an accountant that comes in every payday to do tasks in Sage. It was decreed she will work in X room on a laptop. I made sure I had a cable that would reach the nearest drop. Just imagine talking to the PervasiveSQL Sage database over wifi.
-
@eddiejennings said in To Cable, or Not to Cable:
@dafyre said in To Cable, or Not to Cable:
@scottalanmiller said in To Cable, or Not to Cable:
@dbeato said in To Cable, or Not to Cable:
The only thing I would not run over wifi is VoIP phones, not because of security but stability on the network.
I'd be hesitant to do SAN or database connections over Wifi, too
Can't speak to SAN over WiFi, but databases over Wifi will suck big time -- even if your wifi is reliable.
We have an accountant that comes in every payday to do tasks in Sage. It was decreed she will work in X room on a laptop. I made sure I had a cable that would reach the nearest drop. Just imagine talking to the PervasiveSQL Sage database over wifi.
Ug, does the DB actually get transferred to the endpoint, like QB?
-
@dashrender said in To Cable, or Not to Cable:
@eddiejennings said in To Cable, or Not to Cable:
@dafyre said in To Cable, or Not to Cable:
@scottalanmiller said in To Cable, or Not to Cable:
@dbeato said in To Cable, or Not to Cable:
The only thing I would not run over wifi is VoIP phones, not because of security but stability on the network.
I'd be hesitant to do SAN or database connections over Wifi, too
Can't speak to SAN over WiFi, but databases over Wifi will suck big time -- even if your wifi is reliable.
We have an accountant that comes in every payday to do tasks in Sage. It was decreed she will work in X room on a laptop. I made sure I had a cable that would reach the nearest drop. Just imagine talking to the PervasiveSQL Sage database over wifi.
Ug, does the DB actually get transferred to the endpoint, like QB?
I've never dealt with Quickbooks, but to my knowledge, Sage talks to the DB that lives on a mapped drive, so I don't think any DB files are transferred to the individual workstations.
-
@dashrender said in To Cable, or Not to Cable:
@eddiejennings said in To Cable, or Not to Cable:
@dafyre said in To Cable, or Not to Cable:
@scottalanmiller said in To Cable, or Not to Cable:
@dbeato said in To Cable, or Not to Cable:
The only thing I would not run over wifi is VoIP phones, not because of security but stability on the network.
I'd be hesitant to do SAN or database connections over Wifi, too
Can't speak to SAN over WiFi, but databases over Wifi will suck big time -- even if your wifi is reliable.
We have an accountant that comes in every payday to do tasks in Sage. It was decreed she will work in X room on a laptop. I made sure I had a cable that would reach the nearest drop. Just imagine talking to the PervasiveSQL Sage database over wifi.
Ug, does the DB actually get transferred to the endpoint, like QB?
I think so.
-
@eddiejennings said in To Cable, or Not to Cable:
@dashrender said in To Cable, or Not to Cable:
@eddiejennings said in To Cable, or Not to Cable:
@dafyre said in To Cable, or Not to Cable:
@scottalanmiller said in To Cable, or Not to Cable:
@dbeato said in To Cable, or Not to Cable:
The only thing I would not run over wifi is VoIP phones, not because of security but stability on the network.
I'd be hesitant to do SAN or database connections over Wifi, too
Can't speak to SAN over WiFi, but databases over Wifi will suck big time -- even if your wifi is reliable.
We have an accountant that comes in every payday to do tasks in Sage. It was decreed she will work in X room on a laptop. I made sure I had a cable that would reach the nearest drop. Just imagine talking to the PervasiveSQL Sage database over wifi.
Ug, does the DB actually get transferred to the endpoint, like QB?
I've never dealt with Quickbooks, but to my knowledge, Sage talks to the DB that lives on a mapped drive, so I don't think any DB files are transferred to the individual workstations.
Actually, that's exactly what's happening and what Dash meant. A "real" DB connection is via a DB protocol, never via a mapped drive.
-
@scottalanmiller said in To Cable, or Not to Cable:
@eddiejennings said in To Cable, or Not to Cable:
@dashrender said in To Cable, or Not to Cable:
@eddiejennings said in To Cable, or Not to Cable:
@dafyre said in To Cable, or Not to Cable:
@scottalanmiller said in To Cable, or Not to Cable:
@dbeato said in To Cable, or Not to Cable:
The only thing I would not run over wifi is VoIP phones, not because of security but stability on the network.
I'd be hesitant to do SAN or database connections over Wifi, too
Can't speak to SAN over WiFi, but databases over Wifi will suck big time -- even if your wifi is reliable.
We have an accountant that comes in every payday to do tasks in Sage. It was decreed she will work in X room on a laptop. I made sure I had a cable that would reach the nearest drop. Just imagine talking to the PervasiveSQL Sage database over wifi.
Ug, does the DB actually get transferred to the endpoint, like QB?
I've never dealt with Quickbooks, but to my knowledge, Sage talks to the DB that lives on a mapped drive, so I don't think any DB files are transferred to the individual workstations.
Actually, that's exactly what's happening and what Dash meant. A "real" DB connection is via a DB protocol, never via a mapped drive.
Exactly.
-
Or to put it into really tech terms, it's a shared database file, a system lacking a DBMS.
-
Learn something new and spectacular about Sage every day.
But on a positive note, I learn correct terminology
-
@eddiejennings said in To Cable, or Not to Cable:
Learn something new and spectacular about Sage every day.
But on a positive note, I learn correct terminology
Is it a surprise that it is crap?
-
@scottalanmiller said in To Cable, or Not to Cable:
@eddiejennings said in To Cable, or Not to Cable:
Learn something new and spectacular about Sage every day.
But on a positive note, I learn correct terminology
Is it a surprise that it is crap?
Nope. Just seeing learning more about exactly why it's crap.
-
@eddiejennings said in To Cable, or Not to Cable:
Learn something new and spectacular about Sage every day.
But on a positive note, I learn correct terminology
How old is your sage install?
We have Business Works (formally Business Works Gold). I'm pretty sure they have moved onto a real DB connection. They use a Pervasive DB.
-
Business class databases always have a database server. Even simple websites like a WordPress site use a real RDBMS. Basically, Sage and QB don't see themselves in the same category, or even remotely close, with a little hobby blog site.
-
Which, by extension, tells you a lot about what your accounting and financial staff thinks of the business.
