SmarTeam Multi-Site Diagnostic Services
For those administering an ENOVIA SmarTeam Multi-Site replicated environment, there is an age-old problem in diagnosing and re-synchronizing replicated databases when issues occur. This process has always been tedious and manual. Whether you have two sites in neighboring cities or multiple sites around the world, database transactions are regularly being replicated, with each site synchronizing with the others. For multiple reasons, a site can become corrupted and sometimes have more, less or even different data than other sites. To identify and resolve these problems, Razorleaf is introducing ENOVIA SmarTeam Multi-Site Diagnostic Services. Continue Reading
The Macmillan dictionary defines surface area as the total area of a surface or surfaces, especially the outside surfaces of an object. If we apply this definition to the world of IT security, it refers to the amount of exposure a system has to potential attackers. In Microsoft SQL Server, there are a number of services, ports, and connections that can be configured to control how much “surface area” is exposed. 
The population of 64-bit PCs has steadily increased since their mainstream introduction in 2003, and ENOVIA SmarTeam has supported the use of 64-bit machines since V5R18 SP1. However, saying that a client-server application supports 64-bit machines can mean a number of different things. Let’s take a closer look at how 64-bit Oracle is supported in an ENOVIA SmarTeam environment. 
ENOVIA SmarTeam’s client-server architecture relies on several key connections for successful client operation. When one of these connections is blocked or otherwise unavailable, the client will be unable to login to SmarTeam. Fortunately, most client connection problems can be quickly identified. Read on to learn more about a few common issues and tips on resolving them. 
If you’ve ever tried to pack up and move a SQL Server database from one computer to another, you’ve probably noticed that the permissions and users won’t line up between the two machines. Even if you create accounts with the same usernames on the target machine, the users from one SQL Server are not recognized by the other. As a result, you receive error messages like, ‘Login failed for user USERNAME’. 
Part numbers, quotation numbers, item numbers, revisions, serial numbers…they’re all sequential values that need to be unique, and need to be tracked. In most cases (Design Automation, Product Data Management, CRM, etc.) this means the creation of a database table to hand out and track these identifying numbers and their related data. To ensure that the numbers are unique, most tables will be setup with a unique ID field that will automatically be populated by a database server. But what happens when your ID counter (automatic sequencer) needs to be reset? 
Have you ever wanted to globally replace one value with another inside of a database? Have you ever wanted to globally alter string data, replacing one word with another in a database? If so, the SQL Replace statement could be just what you’re looking for! It allows you to search for one string within another and either remove the string or replace it with a different string. The Replace() statement is available for use on most major database management systems in use today, including Microsoft SQL Server and Oracle. 
