Re: Why?
Or, in MSSQL, doing a 'truncate table' to clear it, a non-transactioned operation..
85 publicly visible posts • joined 16 Sep 2010
Occasionally, yes. Not a high demand for it, but some MDs we use are a bit dated in their operations, and prefer it over email attachments for signed documents. Works just fine, and you manage the Fax phonebook from the PC app. FYI, I can print to it just fine from my android phone via WiFi.
The biggest security issue I have with RDP is that our firewall correctly blocks mapping to shares on the remote system, yet is unable to block a copy/paste operation from local to remote, or vice-versa, while your remote session is open. This includes files, not just text or objects.
- You can charge it in front of your apartment
- You can go get a 'gallon of battery' if the battery dies in a traffic jam, etc.
- The prices are more affordable, as well as less depreciation, and battery replacement cost/disposal/recycling
- The maintenance is affordable
-K-
The database is usually not backed up as a file or set of files. On most common database systems, the backup will back up the database, effectively read only, so as not to block access. Then, any transactions (data changes) after the backup was started will be backed up, usually in a separate operation.
How about Quest Spotlight software for SQL. Needed the port requirements for client/server connections, pre-purchase, for our firewall team, to complete the order process. One web search later, it leads to their support page. However, upon accessing said support page, you get this message: 'You need to be signed in and under a current maintenance contract to view premium knowledge articles.' How is that 'premium knowledge'????
Had something similar at a golf course I worked for. The sub-panel did not have the neutral wire to the distribution panel connected, or it was loose. In any case, lights (incandescent) would be at various brightness levels, or burn out, motors would run fast or slow, or overheat, depending on how balanced the load was on each side of the 110/220 sub-panel. Think of a see-saw board that must be balanced.
I've been pretty satisfied with this one. Print quality is quite good, and it is also has copy/fax/scan- to- network-share as well as wifi/usb/lan interface. It does say 'non-Xerox toner' on power cycles when using generic toner, but has no problem using them; even shows the remaining toner level correctly.
Back in the day when a sheet feeder was a clip-on-the-top option for Diablo daisywheel printers, we had a customer in Phoenix, Arizona with 10 of them. Around 3:30 pm, one printer would start printing on the platen, without loading any paper, almost every day, until maybe 4 pm. We showed up several mornings trying to catch it in the act, not a single mis-feed. Still, most afternoons we would get the service call. We replaced the feeder, the printer, swapped around the printers, to no avail. Turned out the sensor for paper being under the platen was washed out by the sunlight through the office window, on just that one printer, which would only last about 30 minutes. Moving the printer about 2 feet over took care of that one.
The main reason aluminum is bad for house wiring, is that copper is 'springy' and aluminum isn't, at least far less than copper. When the wire is connected to the outlet, switch, etc., it is usually under a screw. The copper will push back when compressed, maintaining a good electrical connection, whereas aluminum doesn't. This leads to a connection that will degrade over time, and cause a 'hot spot' where the wire meets the outlet or switch, increasing the risk of fire.
It's done by having the connectors disconnect the power, excluding ground, first, by having shorter 'fingers' on the connector for those lines. The rest is up to the motherboard having isolation between that connector and the others, so that the drop of all the data lines to basically zero won't affect the other circuitry.
It's actually easy to do this, as the garden-variety (non high-security) keys have a fixed number of pre-defined cut depths, 6 to 10, and number of pins, typically 4 to 6. You just need to recognize the make of key, and try a few different keyway blanks for that make. To make it even easier, some keys have the cut numbers stamped on the head face, such as those by Kwikset and Schlage.
I have always wondered when MS SQL (and some others) would require a WHERE clause on any sort of update or delete statement, instead of defaulting to ALL. I have worked with databases, some literally decades old, that require either a 'WHERE TRUE' or 'WHERE 1=1' qualifier to be syntax-correct. Made this sort of error far more unlikely.