Idera's acquisition of Embarcadero .. Brandon Staggs wrote: I was told in person by someone who would know, who was with Code. Gear,and who is still very prominent at Embarcadero with Delphi, that therewere about a million licenses (assumed this is all Code. Gear dev tools,not just Delphi).
This was back in 2. This is one of the most recurring urban legends about Delphi. Many years ago, someone at EMBT made a guestimate (including estimating piracy) and concluded that a million total copies of Delphi were sold, going back to 1. People here and elsewhere misinterpreted this and began claiming that there were a million Delphi users, and the legend has continued ever since. I have no reason tothink that number is smaller but certainly not 1/1. You have lots and lots and lots of reasons. Simple math is one. If there were one million Delphi customers today, and they a paid $4. EMBT! Keep in mind EMBT bought Codegear for about $3. Is it even remotely realistic to believe that Borland sold a company with that much revenue for that little money? What servers need the most attention when it comes to I/O? When I increase the memory on a server what effect does it have on I/O? The PowerShell daily tip is generated to help educated the PowerShell community. Keep in mind that Idera borrowed $4. EMBT. Those numbers don't even remotely reconcile with the idea of one million active customers (or even semi- active). You also have figures for other languages. Jet. Brains released a C/C++ compiler recently and also released the research they'd done to determine what the C/C++ communities looked like. Their figures concluded that there were 1. C developers worldwide and 4. C++ developers (8. Java). Do you think it remotely plausible that there is one Delphi user for every 2 C developers or every 5 C++ developers? No? Then again, this million active Delphi user idea is ridiculous. Ialso don't think this person was making an outright lie, It's not a lie; it's a misunderstanding that's also based upon John K.'s (I think) back- of- the- envelope estimation. Through a game of telephone the original claim has been wildly distorted. Let's also remember that Code. Gear at the time was.. They continued to insist that Delphi. NET was popular when figures here showed it wasn't, when a German forum shut down their . NET section due to lack of activity, when Torry. Net showed little . NET uploads, when surveys showed few Delphi. NET users compared to VCL, etc. A certain someone claimed access to internal numbers that were in complete contrast to all of measurable reality. What happened? The first thing EMBT did was cancel Delphi. NET, which suggests if such internal numbers existed they were not convincing, to put it politely. Joseph's blind estimates over that information. I didn't make a blind estimate; Embarcadero Insider revealed the estimate inside EMBT. Here's my non- blind estimate. I recently crunched the raw data for the Stack Overflow 2. The number who listed "Delphi" or "Pascal" in their list of primary, currently used technology was 1. A 2. 01. 3 estimate gave the number of developers world wide as approximately 1. M comes out to 9. K, which is nicely in Embarcadero Insider's 5. K- 1. 50. K figure. Toss in those who are maintaining legacy applications with Delphi and it's quite possible to get to 1. K total users (not all current paying customers). By no conceivable manipulation of the Stack Overflow numbers can we get to 1 million or anything close."About a million" is not an unreasonable estimate at all. Brandon, it's completely inconsistent with everything we know about external, objective reality. Think about it - if there were a million users, why would no commercial publisher find it profitable to publish Delphi books in the last 1. That's not even taking into account the missing Delphi jobs. Post this figure to a non- Delphicentric forum and you'll be able to gauge how unreasonable that estimate is by the reaction. Guys, we have to join the fact- based community. We are not one million strong, we are not "as popular as Python" (another claim I recently heard, probably another misconstruing of a ridiculous comment Marco made), we are not "the fastest growing language", etc. We can't fix or improve the language if we don't start from an honest assessment of where we are today. Known issues - SQL Compliance Manager 5. IDERA strives to ensure our products provide quality solutions for your SQL Server needs. The following known IDERA SQL Compliance Manager issues are described in this section. If you need further assistance with any issue, please contact Support (www. Installation and configuration issues. The SQL Compliance Manager 5. Before launching the SQL Compliance Manager 5. Program Files\Idera\SQLcompliance x. Installation Kit or c: \Program Files (x. Idera\SQLcompliance x. Installation Kit. IDERA Dashboard 3. SQL Server 2. 00. SP1. Users should not attempt to install SQL Compliance Manager with IDERA Dashboard 3. SQL Server 2. 00. SP1 as that version of SQL Server is not supported by IDERA Dashboard. SQL Compliance Manager 5. Agent cannot be upgraded using the Management Console or Web Console. An issue in SQL Compliance Manager 5. Agent using the SQL Compliance Manager Management Console or the Web Console. For more information about upgrading to this release, see Upgrade from SQL Compliance Manager 4. Verify SQL Compliance Manager repository database size before upgrading. It is important to check the size of the SQL Compliance Manager repository databases on the Collection Server before proceeding with an upgrade. There are four databases created by SQL Compliance Manager: SQLcompliance; SQLcompliance. Processing; SQLcompliance.< Instance> ; SQLcompliance.< Instance> _Time_Partition. Each database should be under 2. GB to complete a successful upgrade. In order to avoid problems during the upgrade due to database size, IDERA recommends that you regularly archive the repository data to maintain the audit history. For more information about archiving, see Manage Audit Data. If archiving the data through SQL Compliance Manager is not an option at the time of the upgrade, it is recommended to back up the repository databases and delete unneeded records from the Events and Event. SQL tables of the event databases. Case- sensitivity required when specifying the Repository database name. When specifying the location and name of your Repository database, SQL Compliance Manager requires that you use proper capitalization. Agent- Only installation does not create a trace directory when you use a different destination folder. During an Agent- only installation, if you accept the default destination path for SQL Compliance Manager, and then select a different destination drive and use a sub- folder in the Agent Trace Directory dialog box, the installer does not create the Agent Trace Directory during installation. If this issue occurs, reinstall the Agent specifying a folder instead of a sub- folder as the destination path or use the default path specified in the installer. Known issues in version 5. General issues. SQL Compliance Manager does not accept user names longer than 2. Removing databases using the Administration pane in the Management Console does not work. You can remove databases using the Explorer Activity panel. Auditing issues. If the audit settings are configured to audit DML events for a selected table, and extended events is enabled for DML and Select on the Instance, SQL Compliance Manager collects audit data for all tables and not only the selected table. If you turn off extended events, auditing correctly collects data for the selected table only. Execute events are captured when extended events is enabled. There may be some extra events captured and shown through the Extended Events auditing than the events shown through the Trace method. Cannot insert duplicate key row in object 'dbo. Events' with unique index 'IX_Events_event. Id'. Database. Name appears as empty for Login Events. SQL Compliance Manager 5. Database. ID, but do not include the database name. Applying a regulation guideline does not work when there is a Privileged User defined. Case- sensitive collation may prevent some trusted and privileged users from being captured. Before- After data does not appear for Binary Collation SQL Server instances when extended events is enabled. Auditing an Always. On database using the Node method causes the Registered SQL Servers list to display both nodes as Secondary. Audit Snapshot does not include setting to capture DDL SQL statements. Audit settings at an instance level take precedence over database- level settings for a Privileged User. Agent trace folder permissions are overwritten when the Agent is deployed. SQL Compliance Manager attempts to contact the Agent (heartbeat check) on attached archive databases. Users who export reports to Microsoft Excel fail when the SQL text contains more than 3. Some SQL Server startup/stop events may cause the integrity check to fail. The Audit Events tab may display an incorrect user name in the Login column when auditing start and stop server events. A known SQL Server issue causes some SQL Compliance Manager SELECT statements to appear as DML events. This issue occurs when a user audits both SELECT and DML. SQL Compliance Manager captures many events when certain columns are selected from certain system tables from a single SELECT statement query and shows them as individual DML events. Specifically, the SELECT statement which uses the permissions() function generates only DML event traces and not a SELECT event trace. This step results in SQL Compliance Manager reporting the SELECT statement as a DML event. In addition, the permissions() function is deprecated. Microsoft recommends in MSDN documentation that users implement the Has_Perms_By_Name() function instead of the permissions() function. The difference between these two functions is that the permissions() function always generates the DML event traces while the Has_Perms_By_Name() function generates event traces according to permission type used. For example, SELECT event traces for SELECT permission types, and DML event traces for EXECUTE or DELETE permission types. Users who change the default port for the Always. On Availability Group from the default may experience the following issues. SQL Compliance Manager does not accept the name format when attempting to add the listener name using the Cluster Configuration Console. If the port is not added, the agent cannot connect to the SQL Server instance. You can manually add the port to the registry setting later and it will then connect to the instance after restarting the SQLcompliance. Agent. Users cannot connect to the SQL Server instance even when adding the listener with the port in the SQL CM console. The Permissions Check also fails. When you change the definition of a table you are auditing to include BLOB data types, the Before- After data trigger prevents UPDATE, DELETE, and INSERT operations from modifying the table, such as through stored procedures or third- party applications. This issue is most likely to occur when you are auditing all columns in the target table. This issue occurs because Before- After auditing does not support BLOB data types (such as text, image data, or XML code). To correct this issue, change the data definition of the table. SQL Compliance Manager does not support collecting and processing events from encrypted SQL Server trace files. This issue is most likely to occur in environments that use third- party encryption software. For example, some applications can be configured to automatically encrypt all new files created on a specific computer. If you are running encryption software in your SQL Server environment, verify the encryption settings to ensure the application does not encrypt trace files on the audited SQL Server instances. Alerting issues. Filtering by time does not work properly on the Alerts view. Some status alerts including Agent trace directory reached size limit and Collection Server trace directory reached size limit do not display properly in the Web Console. Status alerts are not generated for alert rules of the Agent cannot connect to audited instance Rule Type.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
October 2017
Categories |