4 Replies Latest reply: Apr 7, 2010 8:49 PM by Rob Wunderlich RSS

    SQL Server ODBC Connector Hassle

      When I move my document from my workstation to my QlikView server I have to rebuild the SQL Server ODBC connection string in order to connect to my data source as shown below. I would think that the same connection string would work on both machines provided the data sources are named and configured the same. This is a bit of a hassle and a source or reload errors when we forget to flip the comment tokens. Can anyone suggest what I'm mmissing missing here?




      CONNECT TO VMSProduction (XUserId is LGEJFJVMQbbEHaRIBDdCGIJOPDZUD, XPassword is MbGeFIVOMbcCGZBGRRPB); // Al's Workstation



      //ODBC CONNECT TO [VMS Production] (XUserId is CHfQFJVMQbbEHaRIBDdCGIJOPDZCE, XPassword is YTbCJIVOMbcCGZBGRZTA); // QlikView Server

        • SQL Server ODBC Connector Hassle

          I guess I missed the obvious fact that "VMSProduction" is not the same data source name as "VMS Production". Oops ...

          • SQL Server ODBC Connector Hassle
            Michael Robertshaw

            If the ODBC Connection String has been recreated with exactly the same name then you should be fine. ODBC may be useful when your Dev & Prod environments access a different physical database. If using ODBC then always use SYSTEM datasources, not USER datasources. Generally we recommend using OLEDB whenever possible because it does not require configuration outside the QlikView document and is often faster than ODBC. The OLEDB connection string would always connect to the same physical database though, so might not be appropriate in some restrictive change-control environments.

            You could also set a Variable that indicated which environment you are in (Dev/Prod/etc) and use an IF statement to control the CONNECT statement.