Hot answers tagged

29

Simply run mysql_tzinfo_to_sql /usr/share/zoneinfo | mysql -u root mysql -p $ mysql_tzinfo_to_sql /usr/share/zoneinfo | mysql -u root mysql -p Enter password: Warning: Unable to load '/usr/share/zoneinfo/iso3166.tab' as time zone. Skipping it. Warning: Unable to load '/usr/share/zoneinfo/leap-seconds.list' as time zone. Skipping it. Warning: Unable to load ...


14

SSMS doesn't use ODBC drivers to connect to SQL Server databases. It uses the .Net Framework driver. You cannot choose which driver it uses as it is hard-coded in the application. But why would you need to choose another one? Linked servers are another thing. It is your DB Server itself connecting to another server. If it is SQL Server, it will use its ...


6

As kaiser suggested, the trailing slash is unneeded but without specifying mysql as the database mariadb complains about a missing database. I found that $ mysql_tzinfo_to_sql /usr/share/zoneinfo | mysql -u root -p -Dmysql was the correct way to solve the problem in Mariadb 164.


6

This behaviour has changed in recent updates. See FIX: The value of NUMBER type is truncated when you select data from an Oracle-linked server by using OLE DB provider After you apply this fix, NUMBER values with unknown precision/scale are treated as double values with OLE DB provider. If the precision is important and the range of the values is not ...


5

If the SQL server table is modified will it be automatically reflected in the [linked] table and when? Yes, on next refresh or requery. If I edit the linked Access table will it be reflected in the SQL server table? Yes; as before, these updates will be visible on the other end on next refresh or requery. Trusted Connection only controls how the connection ...


5

The cause of this problem most likely is the primary key of the table in DB2. Access can not handle some data types as primary keys well. Notoriously bad for PKs are all floating point numeric types. They may be rounded differently on the server and in Access. If Access uses a floating point value to query a single record from the server, there will be no ...


5

Not knowing the full details of your issue by your question try the following: Option 1: Temporarily disable Windows Firewall and test your SQL script once more: Option 2: Make sure NetBIOS is enabled in the TCP/IP settings of the network adapter you are using: Option 3: Ensure that SQL Server protocols are enabled through SQL Server Configuration ...


5

Your question is a bit confusing so I hope I'm deciphering it correctly. Technically you can connect to a SAP HANA database using ODBC -- this is helpfully documented in the manual. What you do after you connect is another question. The SAP ERP application schema is very complex and poorly (if at all) documented, and it is highly unlikely that you will be ...


4

Based on my experience with ccure 800 in particular, you do need to have MS Excel and all of the supporting MS Office components installed on the same PC as the ccure Administration client. The OCX libraries are required to support the export function.


4

I used Data Conversion for the varchar larger than 128 as NTEXT but what removed the error for me eventually is the set Validate External Data to False.


4

The client library used to connect does not care at all about the compatibility level of the database. The code issued by the client may have some issues (for example, you needed 90 to use APPLY many years ago). But the mechanism used to send the code and get results does not care


3

In the cCURE 800 Install guide there is a requsite set of software and patches for the OS that need be installed. Including Office XP Web Components and Some patches ( Listed Below) "for Journal Replay and other reports to work" install =Microsoft Office XP Web Components= - [NOTE : f you have office 2003, Access 2003, or Frontpage 2003 installed on your ...


3

OCX files are part of the ActiveX control. There's something wrong with the application and you need to call the vendor to get it fixed.


3

For Access you can use: WHERE obs LIKE '*[#]*' There are three wildcard characters in Access that can be used with LIKE operator: `*` for a string of arbitrary length (equivalent ANSI: `%`) `?` for a single character (equivalent ANSI: `_`) `#` for a single numeric digit `[` for escaping If you want to search for one of those wildcards, you have to ...


3

You don't have to use Access as a mediator. You can look into SSIS or import utility to import data from .TPS to SQL. You have to select Flat file data source. At the end of the import utility, you will have the option to save the package and then schedule it using SQL Agent job. Refer to : How to Migrate Data From Top Speed Database Files Also, look ...


3

I had a similar problem, the fix was a linked table refresh. Access was not aware that the precision had changed in my Oracle table and kept giving me the 'precision too small' error.


3

Apparently this just boils down to SSIS treating any varchar larger than 128 as NTEXT. Not sure why. I can, however, go into the advanced properties of the ODBC source and change the types back to something like DT_WSTR. Which seems to work for the most part. However, I did determine that a few of the tables I'm dealing with actually are carrying upwards of ...


3

The Instant Client is easier to install and more lightweight. It doesn't even need to be installed, you can just unzip it and use it. You don't need an Oracle Home either. On the other hand, it does not support deprecated features like Oracle Names. If you don't need any feature the instant client omits, I suggest you use it. It looks like you are covered ...


3

You should be able to get away with this by creating views in SQL Server that are effectively wrappers for tables in the linked server. You will of course have to deal with the extra layer of security configuration for the linked server, thus ensuring that the Access users are connecting to the external data with the proper credentials (whether it be ...


3

A linked server is referenced just like you would reference a database, with multi-part naming - LinkedSvrName.DBName.SchemaName.ObjectName. There isn't really anything else to "accessing" a linked server. There are some settings you will need to be cognizant of to ensure you can return data; RPC and RPC Out for instance. Also you will want to use ...


3

@Dan, this is by design. SQL Server 2005 is not longer supported. Newly released client drivers support SQL Server 2005+. That said, can you try this? wget https://gallery.technet.microsoft.com/scriptcenter/SQLCMD-and-BCP-for-Ubuntu-c88a28cc/file/142121/1/Ubuntu%2014.04%20MSFT%20ODBC%20Driver.sh sudo bash Ubuntu\ 14.04\ MSFT\ ODBC\ Driver.sh sqlcmd –S ...


3

We had the same issue with legacy applications built around 1998-2007 when we ported SQL Server to a VLAN--for security purposes. Depending on which server we connected to we'd get spurious results--one would work and the other would not...because of a tighter VLAN configuration. Our solution was to "bag" named pipes and to force TCP--as shown below. The ...


3

If you're using SQL Server Management Studio (SSMS), you don't need to "create" a connection via ODBC, you can just connect directly to the server via the SSMS user interface: In SQL Server, the equivalent of an Oracle "database server" is called a "SQL Server Instance". It can contain many databases, which are similar to a "schema" in Oracle. So, when ...


3

MySQL reports with ODBC error numbers which include a SQLSTATE. HY000 is a MySQL ODBC extension for there being no ODBC equivalent error number from the docs on Server Error Codes and Messages A five-character SQLSTATE value ('42S02'). The values are taken from ANSI SQL and ODBC and are more standardized. Not all MySQL error numbers have corresponding ...


3

Place your tnsnames.ora in a directory of your choice, then set the TNS_ADMIN environment variable. Open CMD, enter sysdm.cpl In the Advanced tab, select Environment Variables Under "System Variables", click on 'New' and enter TNS_ADMIN as the name, and the path where your TNSNAMES.ORA resides as your value Windows steps from here. On Linux, it's as easy ...


3

I came to a solution, if anyone is interested: For any reason, firebird ODBC 64-bits driver downloaded from oficial site comes with SQLLEN = 4 bytes. After some help, I managed to compile driver from source code, and the result seems to work with 8 bytes SQLLEN. In the compile proccess, I had a BUILD_DRIVER_VERSION error, modifying line 139 (...


2

Your Access form would need to delete the linked tables, and recreate them in order to continue to have access to the remote table. An interruption of the network connection would certainly cause the symptoms you report. Having said that, you likely shouldn't be having network issues. I'd try to find the cause of the issue, as well as building in the ...


2

I found the following in the source code: This is version 07.05.0001. For those that don't know or don't recall how the versioning works, the major and minor number track the latest release of PostgreSQL that the driver is expected to work with. The revision number is a bit more complex. The first two digits are the version number, where even ...


2

If the parameter to the ODBC prepared statement is defined as decimal(18,0), that's how it's transmitted to the server. The conversion is performed by the ODBC driver. AFAIK the driver is not required by the standard to emit a diagnostic when dropping the fractional part on conversion to an integral type. Presumably the user knows what he's doing. ;-) ...


2

You should be able to create a Linked Server to almost any ODBC data source. I would suggest trying the Microsoft OLE DB Provider for ODBC Drivers. While you need to enter something in the Product Name field, I believe you can enter anything, such as "Firebird". For Data Source, enter the name of the ODBC System DSN you've previously created. You'll need ...


Only top voted, non community-wiki answers of a minimum length are eligible