It would be interesting to see if there are anything of interest (say bacteria) in the water. I believe it is pretty hard to find any water source on earth that doesn't contain anything "alive".
I find the Caps Lock useful here in Canada when typing in your postal code in some form. It is a pain in the butt to type T2K3Y5 with just a "Shift" key.
Rogers and Fido are not the only ones out there. I used to work for a company called KORE Wireless integrating their system with Rogers in Winnipeg (another story), but all they do is offer Sim chips and network usage (no cellphones - meaning you provide the device). They mostly cater to the data crowd, but do have a subset of voice customers also. The nice thing is how the devices work in the US, since they have agreements with most providers you can change towers whenever you want.
P.S. I just goggled KORE, and it looks like they changed their name to KORE Telematics.
Maybe he is right from the standpoint of a vendor, but I work in IT for a large sporting goods store in Canada, and I see lots of benefits when supplying stores.
For example, we don't need to open a box to see what is inside or scan the LPN (license plate) to get the unaudited contents thus giving lots a potential savings in labour and identify shortages. This will help with cross-docking also, where if we know that a box contains X, and X is needed in store A, then we push that box to the other side of the warehouse (shipping), and nothing gets stored. Works fantastic when you have a conveyor system like PUT (an example of one system http://www.ipti.net/puttolight.php) that does all of this for you without human intervention.
I can probably give a dozen more reasons, but these are probably the most important at this point in time.
I work for an agency under DoD and my machine was *not* updated. Perhaps corporate versions of XP are unaffected? I don't know if it would be that choosy to only pick off everything except corporate XP machines. Maybe your firewall is configured to stop this traffic. Get one of the network people to dig up the logs and take a look to see if anything was trying to get through.
You clearly don't understand. What they're trying to do is to create a virtual paradigm shift, and using a collaborative effort, they will fundamentally alter the synergy between these two channels. If they hope to harness the power of Web 2.0, they need to be proactive in their real-time global initiatives, and mesh their current mindshare to make frictionless infrastructures. In other words, it makes ice cubes.
4. Try putting in a ReadyBoost-compatible (you probably won't know if it is until you've tried:-p) USB memory stick and have Vista manage it as extra RAM. It's not really RAM-fast or anything (but it doesn't seem to make things worse at least), but especially seeemed to cut a bit on hard drive access. I'm not sure, but it's possible it relocates some of its swap file to it as ReadyBoost kicks in. Now I have another purpose for all the vendor-shwag USB sticks.
True, as long as you do this:
SELECT * FROM table1 WHERE id = @id
But, if the SQL is dynamic:
SELECT * FROM table1 WHERE id = 1
SELECT * FROM table1 WHERE id = 2
SELECT * FROM table1 WHERE id = 3
SELECT * FROM table1 WHERE id = 4
Then the server has to create a new plan every time. I have seen this all too often on the client side code.
Just to appending to this list:
4. Get your servers clustered and this will help with server load (not really necessary at this this time for what you need, but will position you for the future) and redundancy if the server dies. If this is not possible, look at "warm" backups. But then again ask the business side what is their expectation when a problem happens, and then plan for it.
5. For performance tuning look at the execution plans on the SQL
6. Use transactions whenever possible (BEGIN TRANSACTION / COMMIT / ROLLBACK).
7. If you see deadlocks on tables, try using table hints (NOLOCK) on SELECT statements.
8. Get an experienced DBA to peer-review your setup and code if necessary.
And a change to 1. You can use stored procs as well as views and functions. But moving the SQL code into views / functions will bring performance gains from the server by having the code already compiled and creating a saved execution plan.
Slashdot Mirror
It is also interesting to note that Firefox 3 beta 4 scored a 68 / 100 on the Acid3 test.
Gives a whole new meaning to "Don't tase me bro!"
Any chances in the future that NASA will try a Star Dust mission to retrieve some of this water? ( http://www.nasa.gov/mission_pages/stardust/main/index.html/ )
It would be interesting to see if there are anything of interest (say bacteria) in the water. I believe it is pretty hard to find any water source on earth that doesn't contain anything "alive".
To be fair, Vista has a gorgeous interface. Very nice on the eyes, but leaves a lot to the imagination functionally.
And has Dorvak written an op-ed on it too?
I find the Caps Lock useful here in Canada when typing in your postal code in some form. It is a pain in the butt to type T2K3Y5 with just a "Shift" key.
WORD
Question: Has anyone tried to run Microsoft's DRM solution through WINE?
Rogers and Fido are not the only ones out there. I used to work for a company called KORE Wireless integrating their system with Rogers in Winnipeg (another story), but all they do is offer Sim chips and network usage (no cellphones - meaning you provide the device). They mostly cater to the data crowd, but do have a subset of voice customers also. The nice thing is how the devices work in the US, since they have agreements with most providers you can change towers whenever you want.
P.S. I just goggled KORE, and it looks like they changed their name to KORE Telematics.
Maybe he is right from the standpoint of a vendor, but I work in IT for a large sporting goods store in Canada, and I see lots of benefits when supplying stores.
For example, we don't need to open a box to see what is inside or scan the LPN (license plate) to get the unaudited contents thus giving lots a potential savings in labour and identify shortages. This will help with cross-docking also, where if we know that a box contains X, and X is needed in store A, then we push that box to the other side of the warehouse (shipping), and nothing gets stored. Works fantastic when you have a conveyor system like PUT (an example of one system http://www.ipti.net/puttolight.php) that does all of this for you without human intervention.
I can probably give a dozen more reasons, but these are probably the most important at this point in time.
I have done the same. XP for gaming and Ubuntu for everything else, and once I get Wine to work with the rest of my games, then XP will be gone too.
And we Canadians are "supposedly" spying on the Americans too. Maybe the Chinese should emulate this: http://www.ctv.ca/servlet/ArticleNews/story/CTVNew s/20070507/spy_coin_070507/20070507
Wonders never cease. Nice work. I guess hell just froze over.
I realize that this is an issue under Windows, but can this cause issues in Linux?
Also, can we see the directory and the contents and determine the reasons behind this?
As long as it stars Ben Stiller and Owen Wilson. It will probably win an Oscar too.
I really hope there is intelligent life out there, since there is a lack of it here on Earth.
True, as long as you do this: SELECT * FROM table1 WHERE id = @id But, if the SQL is dynamic: SELECT * FROM table1 WHERE id = 1 SELECT * FROM table1 WHERE id = 2 SELECT * FROM table1 WHERE id = 3 SELECT * FROM table1 WHERE id = 4 Then the server has to create a new plan every time. I have seen this all too often on the client side code.
Just to appending to this list:
4. Get your servers clustered and this will help with server load (not really necessary at this this time for what you need, but will position you for the future) and redundancy if the server dies. If this is not possible, look at "warm" backups. But then again ask the business side what is their expectation when a problem happens, and then plan for it.
5. For performance tuning look at the execution plans on the SQL
6. Use transactions whenever possible (BEGIN TRANSACTION / COMMIT / ROLLBACK).
7. If you see deadlocks on tables, try using table hints (NOLOCK) on SELECT statements.
8. Get an experienced DBA to peer-review your setup and code if necessary.
And a change to 1. You can use stored procs as well as views and functions. But moving the SQL code into views / functions will bring performance gains from the server by having the code already compiled and creating a saved execution plan.
I think Google has prior art here. http://www.google.com/tisp/install.html