And in SQL Server. ' is used to delimit strings in SQL Server. If the setting QUOTED_IDENTIFIER is set off (which is not the default under SQL Server 7 or 2K) then something enclosed in " will be treated as a string, if QUOTED_IDENTIFIER is set on anything enclosed in " will be treated as a column name rather than as a string.
It only runs on one OS family which is a huge limit on hardware choice.
OK.
SQL Server triggers do not have as many features as, e.g. DB2.
I don't know much about DB2, so I can't comment on feature comparisons, however I'd feel that by the time you hit SQL Server 2000 you can do pretty much whatever you want to do using the SQL Server triggers.
SQL Server has a lower limit on the number of indexes per table than other RDBMSs.
I think if you hitting 250 indexs/table than your database design is unusual. Assuming that you have a properly normailsed design, at that point you are likely to run into a performance hit due to the overhead on inserts, updates etc. You'd be better off moving to an OLAP design.
Other RDBMSs are more tunable (have more exposed parameters).
OK.
My point to the ealier the_mink was that it is pretty stupid to bash MS products simply because they are MS.
I have yet to hear negative comments on SQL Server unless they are anti-MS motivated or are complaints about the price. On the other hand I hear a lot of comments on how good it is from a lot of people. I spend a lot of time working with different databases.
The article is making a mistake in comparing Australia to Hong Kong and Japan. Australia is a country with a relatively small population spread out over large distances. One problem that the telicos are facing is do you run cable 100km out to a town of 1000 people?
Much of the population in Australia is concentrated in the cities, however even the cities are not comparable to most other coutries, the reason being that everyone wants a house on a 1/4 acre block. I have heard it said that Australia is *geographically* the largest city in the world with a population of only 4-5 million. The issue is one of density, the telicos don't neccessarily get a good ROI for installing services.
I'd suggest that you do a search through the archive of Bugtraq for postings on Windows update. The long and the short of it is that it doesn't always work and buggy patches have been released. If you leave this 'feature' on you can still get hacked. If you are serious about security you lock the machine down (in which case you may be protected from vulnerabilities even if not patched, eg Sapphire not a problem if the correct ports are blocked) and test the patches on a test box to see what their effect will be.
One question: does the average home user have time for this?
I should say that I write use MS sfotware products more than any other and that I really like some of their stuff, however their process of patching is a big problem and it is high time it was addressed.
I found a bug in IE6, or failing that an undocumented "feature". Then I found out that there is no way to report bugs to microsoft. Clearly this is because there are no bugs in Microsoft products.
As of a year or so ago the process was to send an email to ms-wish@microsoft.com. Says it all really. They are not interested in bug reports, they are merely interested in new features.
Slashdot Mirror
And in SQL Server. ' is used to delimit strings in SQL Server. If the setting QUOTED_IDENTIFIER is set off (which is not the default under SQL Server 7 or 2K) then something enclosed in " will be treated as a string, if QUOTED_IDENTIFIER is set on anything enclosed in " will be treated as a column name rather than as a string.
It only runs on one OS family which is a huge limit on hardware choice.
OK.
SQL Server triggers do not have as many features as, e.g. DB2.
I don't know much about DB2, so I can't comment on feature comparisons, however I'd feel that by the time you hit SQL Server 2000 you can do pretty much whatever you want to do using the SQL Server triggers.
SQL Server has a lower limit on the number of indexes per table than other RDBMSs.
I think if you hitting 250 indexs/table than your database design is unusual. Assuming that you have a properly normailsed design, at that point you are likely to run into a performance hit due to the overhead on inserts, updates etc. You'd be better off moving to an OLAP design.
Other RDBMSs are more tunable (have more exposed parameters).
OK.
My point to the ealier the_mink was that it is pretty stupid to bash MS products simply because they are MS.
Care to justify that comment?
I have yet to hear negative comments on SQL Server unless they are anti-MS motivated or are complaints about the price. On the other hand I hear a lot of comments on how good it is from a lot of people. I spend a lot of time working with different databases.
Have you seen the Darwin awards page where the guy drank liquid nitrogen? One cool dude
The article is making a mistake in comparing Australia to Hong Kong and Japan. Australia is a country with a relatively small population spread out over large distances. One problem that the telicos are facing is do you run cable 100km out to a town of 1000 people?
Much of the population in Australia is concentrated in the cities, however even the cities are not comparable to most other coutries, the reason being that everyone wants a house on a 1/4 acre block. I have heard it said that Australia is *geographically* the largest city in the world with a population of only 4-5 million. The issue is one of density, the telicos don't neccessarily get a good ROI for installing services.
I'd suggest that you do a search through the archive of Bugtraq for postings on Windows update. The long and the short of it is that it doesn't always work and buggy patches have been released. If you leave this 'feature' on you can still get hacked. If you are serious about security you lock the machine down (in which case you may be protected from vulnerabilities even if not patched, eg Sapphire not a problem if the correct ports are blocked) and test the patches on a test box to see what their effect will be.
One question: does the average home user have time for this?
I should say that I write use MS sfotware products more than any other and that I really like some of their stuff, however their process of patching is a big problem and it is high time it was addressed.
No joke. Last year at Uni I was writing C for DOS. This is in the final year of a Mechtronics degree. I think they are not planning to move to QNX.
I found a bug in IE6, or failing that an undocumented "feature". Then I found out that there is no way to report bugs to microsoft. Clearly this is because there are no bugs in Microsoft products. As of a year or so ago the process was to send an email to ms-wish@microsoft.com. Says it all really. They are not interested in bug reports, they are merely interested in new features.