Safe to use SQL-Anywhere Version 9?

I have inherited a server running SQL-Anywhere Version 9, I believe that version is end-of-life. I'm trying to come up with good arguments for replacing that version with a newer one, but the boss isn't interested in replacing it. Can anyone help me with arguments?

mobrien022 wrote:
Is it safe to use a different version of JAVA for compilation (javac.exe) vs runtime (java.exe)?
If so, is there a rule of thumb like:
"the javac.exe should be from a newer JDK than the JDK/JRE containing the java.exe" or
"the javac.exe should be from an older JDK than the JDK/JRE containing the java.exe"There's a twist: you can pass the compiler -source and -target options so that it is compiled for an older version. If you don't do that you'll see that an older java.exe kraps out immediately when given a newer version in class files.

Similar Messages

Sybase with ase and sql anywhere 16 using ssma

ok this may sound like a very dumb question but how does one connect to sybase central (sql 16 anywhere) using ssma.
In my ase connections when i do test connection it returns successful however when i click on ssma > connect to sybase it returns
ERROR [08001] [SAP][ASE ODBC Driver]Client unable to establish a connection
i have my network server running on sybase using sql anywhere 16 network server.
I also had my firewalls off
any help would be appreciated.

Hi Jeff ,
Thank you so much for the reply.
I have used 32 bit PHP.
But now we have resolved above mentioned issue. Now we can connect PHP with SQL Anywhere successfully.
Regards,
Vishal Chikhalikar
PHP Programmer

ODBC Gateway on Linux error - connects ok with Sybase SQL Anywhere

OS: CentOS 5.8 64-bit
DB: Oracle XE 11gR1 64-bit
Gateway: Oracle Gateway for ODBC 64-bit
Database and gateway reside on same Linux Server.
Connecting to remote Sybase SQL Anywhere 10 server on WindowsXP.
Using SQL Anywhere 11 odbc driver and unixODBC driver manager on Linux server.
isql tool connects without any problems.
One LISTENER, service for db and gateway on same port.
===================================
Via SQL*Plus, the following error occurs....
SQL> select * from dual@dblink;
select * from dual@dblink
ERROR at line 1:
ORA-28513: internal error in heterogeneous remote agent
ORA-02063: preceding line from dblink
===================================
sqlnet.ora
# sqlnet.ora Network Configuration File: /u01/app/oracle/product/11.2.0/xe/network/admin/sqlnet.ora
# Generated by Oracle configuration tools.
NAMES.DIRECTORY_PATH=(TNSNAMES)
ADR_BASE = /u01/app/oracle/product/11.2.0/xe
==================================
tnsnames.ora
# tnsnames.ora Network Configuration File:
XE =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = mysystem)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = XE)
dblink =
(DESCRIPTION =
(ADDRESS =
(PROTOCOL = TCP)(HOST = mysystem)(PORT = 1521)
(CONNECT_DATA =
(SID = dblink))
(HS=OK))
EXTPROC_CONNECTION_DATA =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC_FOR_XE))
(CONNECT_DATA =
(SID = PLSExtProc)
(PRESENTATION = RO)
=======================
listener.ora
# listener.ora Network Configuration File:
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SID_NAME = PLSExtProc)
(ORACLE_HOME = /u01/app/oracle/product/11.2.0/xe)
(PROGRAM = extproc)
(SID_DESC =
(SID_NAME = dblink)
(ORACLE_HOME = /u01/app/oracle/product/11.2.0/gtw)
(PROGRAM = dg4odbc)
(ENVS=LD_LIBRARY_PATH=/opt/sqlanywhere11/lib64:/u01/app/oracle/product/11.2.0/gtw/lib)
LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC_FOR_XE))
(ADDRESS = (PROTOCOL = TCP)(HOST = mysystem)(PORT = 1521))
DEFAULT_SERVICE_LISTENER = (XE)
========================
initdblink.ora
# This is a sample agent init file that contains the HS parameters that are
# needed for the Database Gateway for ODBC
# HS init parameters
HS_FDS_CONNECT_INFO=dblink
HS_FDS_SHAREABLE_NAME=/usr/lib64/libodbc.so
HS_FDS_TRACE_LEVEL=255
HS_LANGUAGE=american_america.we8iso8859p1
HS_NLS_NCHAR=UTF-8
# ODBC specific environment variables
set ODBCINI=/etc/odbc.ini
========================
Oracle Corporation --- MONDAY OCT 15 2012 17:23:39.915
Heterogeneous Agent Release
11.2.0.1.0
Oracle Corporation --- MONDAY OCT 15 2012 17:23:39.914
Version 11.2.0.1.0
Entered hgogprd
HOSGIP for "HS_FDS_TRACE_LEVEL" returned "255"
Entered hgosdip
setting HS_OPEN_CURSORS to default of 50
setting HS_FDS_RECOVERY_ACCOUNT to default of "RECOVER"
setting HS_FDS_RECOVERY_PWD to default value
setting HS_FDS_TRANSACTION_LOG to default of HS_TRANSACTION_LOG
setting HS_IDLE_TIMEOUT to default of 0
setting HS_FDS_TRANSACTION_ISOLATION to default of "READ_COMMITTED"
HOSGIP returned value of "UTF-8" for HS_NLS_NCHAR
setting HS_FDS_TIMESTAMP_MAPPING to default of "DATE"
setting HS_FDS_DATE_MAPPING to default of "DATE"
setting HS_RPC_FETCH_REBLOCKING to default of "ON"
setting HS_FDS_FETCH_ROWS to default of "100"
setting HS_FDS_RESULTSET_SUPPORT to default of "FALSE"
setting HS_FDS_RSET_RETURN_ROWCOUNT to default of "FALSE"
setting HS_FDS_PROC_IS_FUNC to default of "FALSE"
setting HS_FDS_CHARACTER_SEMANTICS to default of "FALSE"
setting HS_FDS_MAP_NCHAR to default of "TRUE"
setting HS_NLS_DATE_FORMAT to default of "YYYY-MM-DD HH24:MI:SS"
setting HS_FDS_REPORT_REAL_AS_DOUBLE to default of "FALSE"
setting HS_LONG_PIECE_TRANSFER_SIZE to default of "65536"
setting HS_SQL_HANDLE_STMT_REUSE to default of "FALSE"
setting HS_FDS_QUERY_DRIVER to default of "TRUE"
setting HS_FDS_SUPPORT_STATISTICS to default of "FALSE"
Parameter HS_FDS_QUOTE_IDENTIFIER is not set
setting HS_KEEP_REMOTE_COLUMN_SIZE to default of "OFF"
setting HS_FDS_GRAPHIC_TO_MBCS to default of "FALSE"
setting HS_FDS_MBCS_TO_GRAPHIC to default of "FALSE"
Default value of 64 assumed for HS_FDS_SQLLEN_INTERPRETATION
setting HS_CALL_NAME_ISP to "gtw$:SQLTables;gtw$:SQLColumns;gtw$:SQLPrimaryKeys;gtw$:SQLForeignKeys;gtw$:SQLProcedures;gtw$:SQLStatistics;gtw$:SQLGetInfo"
setting HS_FDS_DELAYED_OPEN to default of "TRUE"
setting HS_FDS_WORKAROUNDS to default of "0"
Exiting hgosdip, rc=0
ORACLE_SID is "dblink"
Product-Info:
Port Rls/Upd:1/0 PrdStat:0
Agent:Oracle Database Gateway for ODBC
Facility:hsa
Class:ODBC, ClassVsn:11.2.0.1.0_0008, Instance:dblink
Exiting hgogprd, rc=0
hostmstr: 0: HOA After hoagprd
Invalid HS_NLS_NCHAR value UTF-8 specified
Setting HS_NLS_NCHAR to Server Default 2000
Invalid HS_NLS_NCHAR value UTF-8 specified
Setting HS_NLS_NCHAR to Server Default 2000
hostmstr: 0: HOA Before hoainit
Entered hgoinit
HOCXU_COMP_CSET=1
HOCXU_DRV_CSET=31
HOCXU_DRV_NCHAR=2000
HOCXU_DB_CSET=873
HOCXU_SEM_VER=112000
Exiting hgoinit, rc=28513
hostmstr: 0: HOA After hoainit
RPC Calling nscontrol(0), rc=0
hostmstr: 0: RPC Before Exit Agent
hostmstr: 0: HOA Before hoaexit
Entered hgoexit
HS Gateway: NULL connection context at exit
Exiting hgoexit, rc=0 with error ptr FILE:hgoexit.c LINE:108 FUNCTION:hgoexit() ID:Connection context
hostmstr: 0: HOA After hoaexit
hostmstr: 0: RPC After Exit Agent
=============================
Also, does anyone know how to determine the location (full path) of the unixODBC driver manager ?
Please assist if you can...thx.
Edited by: user601798 on Oct 15, 2012 3:37 PM

Let me start with the unixODBC driver:
There's no generic location as it depends which package you've used to install the UnixODBC driver manager or how you compiled it from scratch. I commonly prefer to compile it from scratch as this offers me to install it to any location I like.
If you're not sure where it is located, you could perform a search on your machine looking for libodbc.so. Then cross check it with "file <location>/libodbc.so" to see the lib is a 64bit library.
So let's assume in the /usr/lib64 you found the libodbc.so library, then the setting
HS_FDS_SHAREABLE_NAME=/usr/lib64/libodbc.so
is correct. Else you need to adopt the parameter.
Next step is to check out which unixODBC version is installed. That's commonly done by calling "odbcinst -j".
Looking now ta the gateway init file there's a parameter HS_NLS_NCHAR set to UTF-8. UnixODBC is commonly compiled with UCS2 support, so please change it to HS_NLS_NCHAR=UCS2
Could you also please post the content of the odbc.ini file "more /etc/odbc.ini"?
Thanks,
Klaus

Problems with JConnect, Sybase SQL Anywhere 5.x

Hi
I use Sybase SQL Anywhere 5.x, Apache Server, Apache Jserver.(WINNT)
I must to write servlet, which connects to Sybase database using JConnect.
When database is on the same host as Apache server, and my servlet i run services:
Open Server Gateway (dbos50.exe <server_name>), where server_name in sql.ini is
"master=NLWNSCK,x.x.x.x,8001" (x.x.x.x is my IP)
Standalone Engine (dbeng50.exe <path to the database>)
And all is ok
But I don't known, what to do, when my database is on other host, neither my servlet(aplication and JConnect)
Which services I must run on Host, where database is?
Which services I must run on Host, where JConnect and servlet(aplication) are?
Must I use Cascade Gateway or TDS tunneling?
Can you help me?
Thanks.

Hi,
I need to connect to Sybase SQL Anywhere version 5.5.05, too, but I can't find the driver to connect to the server, could u tell me about this? Please share it with if available.
thanks.

Afaria Database on SQL Anywhere 12 and Replication

Hi,
I have Afaria Farm and I Use SQL Anywhere 12 as database server.
I want to replicate this database to another SQL Anywhere 12 Server.
Which one is good way to replication
And can I have some documentation that tells this step by step?
I am not a DB admin.

Hello Tevfik,
I think we need to understand your requirements a little more: why are you interested in SQL Anywhere replication and what are your plans for it?
If you're looking for an always-available SQL Anywhere database for Afaria, there is high-availability (database mirroring). This will allow you to maintain two database server partners (with a third arbiter), where the primary has read/write capabilities and the mirror partner is read-only. There is a tutorial here in the documentation.
If you're looking for a reporting server to do read-only queries for reporting, there is read-only scale out (copy nodes). The tutorial can be found here.
Are you trying to keep a backup copy of your database via replication? If so, you may want to consider live backups (see the wiki), or just regular backups (also see the wiki). Regular backups should still be used in conjunction with any of the high-availability scenarios described above.
If you're really looking for data movement, particularly to multiple database nodes, there is synchronization to other enterprise databases (including SQL Anywhere, but this also includes HANA, ASE, IQ, etc.) with MobiLink and replication to other SQL Anywhere databases, via SQL Remote. MobiLink uses a session-based HTTP or TCP/IP connection as a transport, while SQL Remote can use offline FILE, FTP, SMTP, and online HTTP as a transport.
You may read elsewhere that historically SQL Anywhere can also be used with SQL Remote for Adaptive Server Enterprise (ASE) or Replication Server for replication, but both of these methods have been deprecated and removed in current versions and are not supported by development.
Regards,
Jeff Albion
SAP Active Global Support

PocketBuilder 2.5.2 and SQL Anywhere 12

Hi all,
I have a Windows Mobile device . It should run SQL Anywhere 12 with Pocket Builder 2.5.2. But at the start on the mobile device always get the message that the driver dbodbc10.dll missing . Where can I set that the driver of ASA 12 should be taken ? Or does this not work with ASA 12 .
Thanks for help.
André Rust

Hello Andre,
PocketBuilder 2.5.x is not supported and no longer sold anymore. Moreover, it has not been tested against ASA 12:
Software used for database connection
You might try what is explained below from link SyBooks Online (Archive)
Connecting to a SQL Anywhere database
By default, PocketBuilder runtime applications on the Windows CE device use
the PKODB25.DLL dynamic link library to connect to SQL Anywhere data
sources through the SQL Anywhere version 10 ODBC driver (dbodbc10.dll).
You can specify a different ODBC driver by including the
driver=dbodbcX.dll parameter in your DBPARM
ConnectString assignment or in the file data source, where X is
the version number of the ODBC driver for Adaptive Server Anywhere or SQL
Anywhere.
For example, to use the Adaptive Server Anywhere 9 ODBC driver on the Windows
CE device, you can use the following DBPARM:
SQLCA.DBPARM="ConnectString='DSN=myDSN;driver=dbodbc9.dll;UID=dba;PWD=sql'"
CONNECT using SQLCA;
SQLCA is the default connection object in all PocketBuilder environments.
In all runtime environments, the connect string for the DBPARM parameter must
not include spaces other than those in the data source name (DSN). The DSN you
assign must exist in the root directory on the Windows CE device or emulator.
When you install the complete PocketBuilder runtime package to the device or
emulator (rather than just the runtime DLLs), the ASA 9.0 Sample.DSN file
is added to the root directory. Instead of using the ConnectString DBPARM to set
the driver name, you can modify ASA 9.0 Sample.DSN, or any other DSN file
that you use, so that it includes an assignment for the database driver:
[ODBC] enginename=asademo databasename=asademo databasefile=\Program Files\Sybase\ASA\asademo.db start=\Program Files\Sybase\ASA\dbsrv9.exe Driver=dbodbc9.dll
If you are using the ASA Sample database that is migrated to SQL Anywhere 10,
you can deploy the DemoDB_SA10.DSN file with your application. The
PocketBuilder setup program installs this DSN file in the PocketBuilder
Code Examples\SADemoData\SA10 directory. The DSN file sets the the
databse file to \Program Files\SQLAny10\ASADemo_10.db, and the driver
name to dbodbc.dll.
SQL Anywhere requires that DSN files be saved in ANSI format rather than
Unicode format.
If you are running your PocketBuilder applications from the desktop, it is
recommended that you use the actual name of the driver (for example, “Adaptive
Server Anywhere 9.0”) in a ConnectString DBPARM rather than the name of the DLL.
Otherwise, the driver you select in the connection string might be ignored.
HTH
Jacob

Error when using sql developer

my computer lost power while i was using sql developer (version 1.1.0.23). i restarted and logged in and now any time i try to access a saved db connection or go to tools prefernces, database and any parameters i get the following error or something very similar.
ava.lang.NullPointerException
     at oracle.dbtools.raptor.conntypes.RaptorClassLoader.findClassLoader(RaptorClassLoader.java:48)
     at oracle.dbtools.raptor.conntypes.RaptorConnectionWrapper.createConnectionImpl(RaptorConnectionWrapper.java:202)
     at oracle.dbtools.raptor.conntypes.RaptorConnectionWrapper.createConnection(RaptorConnectionWrapper.java:160)
     at oracle.dbtools.raptor.conntypes.RaptorConnectionWrapper.getJdbcConnection(RaptorConnectionWrapper.java:191)
     at oracle.dbtools.raptor.conntypes.RaptorConnectionWrapper.getPresentation(RaptorConnectionWrapper.java:66)
     at oracle.dbtools.raptor.utils.Connections$ConnectionInfo.createConnection(Connections.java:738)
     at oracle.dbtools.raptor.utils.Connections$ConnectionInfo$ConnectRunnable.doWork(Connections.java:611)
     at oracle.ide.dialogs.ProgressRunnable.run(ProgressRunnable.java:159)
     at oracle.ide.dialogs.ProgressBar.run(ProgressBar.java:553)
     at java.lang.Thread.run(Thread.java:619)

Download the latest and Greatest 3.1 at :http://www.oracle.com/technetwork/developer-tools/sql-developer/overview/index.html
1.1 is a very old version
Michael

SQL Developer Version 1.5.1 Build MAIN-5440 Imported Connections missing

I have a problem using SQL Developer Version 1.5.1 Build MAIN-5440. I have successfully imported connections from my previous version of SQL Developer. After I restart, all the connections I have imported has been gone. I tried to import the connections but got an error message:
java.lang.NullPointerException
     at oracle.jdeveloper.db.DatabaseConnections.getReferenceable(DatabaseConnections.java:695)
     at oracle.jdeveloper.db.DatabaseConnections.addConnection(DatabaseConnections.java:762)
     at oracle.dbtools.raptor.connections.ConnectionGrinder.doImportExport(ConnectionGrinder.java:243)
     at oracle.dbtools.raptor.connections.ConnectionGrinder.invoke(ConnectionGrinder.java:117)
     at oracle.dbtools.raptor.navigator.DatabaseNavigatorController.handleEvent(DatabaseNavigatorController.java:200)
     at oracle.ide.controller.IdeAction.performAction(IdeAction.java:524)
     at oracle.ide.controller.IdeAction.actionPerformedImpl(IdeAction.java:855)
     at oracle.ide.controller.IdeAction.actionPerformed(IdeAction.java:496)
     at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1849)
     at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2169)
     at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:420)
     at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:258)
     at javax.swing.AbstractButton.doClick(AbstractButton.java:302)
     at javax.swing.plaf.basic.BasicMenuItemUI.doClick(BasicMenuItemUI.java:1000)
     at javax.swing.plaf.basic.BasicMenuItemUI$Handler.mouseReleased(BasicMenuItemUI.java:1041)
     at java.awt.Component.processMouseEvent(Component.java:5488)
     at javax.swing.JComponent.processMouseEvent(JComponent.java:3126)
     at java.awt.Component.processEvent(Component.java:5253)
     at java.awt.Container.processEvent(Container.java:1966)
     at java.awt.Component.dispatchEventImpl(Component.java:3955)
     at java.awt.Container.dispatchEventImpl(Container.java:2024)
     at java.awt.Component.dispatchEvent(Component.java:3803)
     at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4212)
     at java.awt.LightweightDispatcher.processMouseEvent(Container.java:3892)
     at java.awt.LightweightDispatcher.dispatchEvent(Container.java:3822)
     at java.awt.Container.dispatchEventImpl(Container.java:2010)
     at java.awt.Window.dispatchEventImpl(Window.java:1774)
     at java.awt.Component.dispatchEvent(Component.java:3803)
     at java.awt.EventQueue.dispatchEvent(EventQueue.java:463)
     at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:242)
     at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:163)
     at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:157)
     at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:149)
     at java.awt.EventDispatchThread.run(EventDispatchThread.java:110)
I tried to create a new connections. I can test the newly created connections but cannot save it.

This bug was fixed in SqlDev 2.1.1. You'll find this build on our homepage.
-Raghu

Problems using SQL*Loader with Oracle SQL Developer

I have been using TOAD and able to import large (milllions of rows of data) in various file formats into a table in an Oracle database. My company recently decided not to renew any more TOAD licenses and go with Oracle SQL Developer. The Oracle database is on a corporate server and I access the database via Oracle client locally on my machine. Oracle SQL Developer and TOAD are local on my desktop and connected through TNSnames using the Windows XP platform. I have no issues with using SQL*Loader via the import wizard in TOAD to import the data in these large files into an Oracle table and producing a log file. Loading the same files via SQL*Loader in SQL Developer, freezes up my machine and I cannot get it to produce a log file. Please help!

I am using SQL Developer version 3.0.04. Yes, I have tried it with a smaller file with no success. What is odd is that the log file is not even created. What is created is a .bat file a control file and a .sh file but no log file. The steps that I take:
1.Right click on the table I want to import to or go to actions
2. Import Data
3. Find file to import
4. Data Preview - All fields entered according to file
5. Import Method - SQL Loader utility
6. Column Definitions - Mapped
7. Options - Directory of files set
8. Finish
With the above steps I was not able to import 255 rows of data. No log file was produced so I don't know why it is failing.
thanks.
Edited by: user3261987 on Apr 16, 2012 1:23 PM

How to use SQL Developer Debugger

I'm using SQL Developer Version 3.2.20.09 and want to use its debugger option. I tried to get "how to use SQL Developer Debugger" by using google.ca but didn't get any tutorial. I really appreciate if someone suggest me any good and simple tutorial regarding SQL Developer Debugger, Thanks in advance.

Hello,
you can find a tutorial here:
http://www.oracle.com/webfolder/technetwork/tutorials/obe/db/devdays2012/mod2_sqldev/mod2_sqldev.html
Joop

SQL Anywhere Database Developer Certification

Hello All,
I am using sql anywhere since last 3 years and now, I am planning to go for SQL anywhere database developer certificate.
Please suggest me any exam course which is suitable for the same.
Thanks,

Hi Anal,
You can search for existing SAP certification exams in the link below
SAP Certifications | Training & Education | SAP | SAP
However, I have not found a SQL Anywhere certification course/exam.
Mirco

Execute the SSIS packages (2008 version) using SQL job 2008

We need to execute the SSIS packages (2008 version) using SQL job Please help with details information how to execute it.
1.Protection level of the SSIS packages.
2.Configuration File (Curently using XML file)
3.Please provide details how to create Credential (Windows User etc) Do we need to create windows cred explicitly to run the Job etc..
4.Please provide details for creating Proxy.
5.How can we configure the xml file since the xml is reading from local box but when the package is moved from developement box to production box
then the local drive might not be mapped with Production box .
6.Roles that need to be tagged for the Proxy/Credential.
7.Which is the best and safest way to execute ssis packages either msdb deployment or filesystem deployment and other necessary details.

Hi,
If you want to Execute your SSIS package using SQL job then best solution is to first deploy your Package
either using msdb deployment or filesystem deployment.The simplest approach to deployment is probably to deploy to the file system.
So, here is the deployment steps;
There are four steps in the package deployment process:
    The first optional step is optional and involves creating package
configurations that update properties of package elements at run time. The configurations are automatically included when you deploy the packages.
    The second step is to build the Integration Services project to create a package deployment utility. The deployment utility for the project contains the packages that you want to deploy
    The third step is to copy the deployment folder that was created when you built the Integration Services project to the target computer.
    The fourth step is to run, on the target computer, the Package Installation Wizard to install the packages to the file system or to an instance of SQL Server.
you can use below link also;
http://bharath-msbi.blogspot.in/2012/04/step-by-step-ssis-package-deployment.html
After that you need to Schedule package using SQL Agent then Have a look at the following link. It explains how to create an SQL job that can execute an SSIS package on a scheduled basis.
http://www.mssqltips.com/sqlservertutorial/220/scheduling-ssis-packages-with-sql-server-agent/
Deployment in msdb deployment or filesystem deployment has there own merits and demerits.
For security point of view msdb deployment is good.
it provides Benefits from database security, roles and Agent interaction
Protection Level;
In SQL Server Data Tools (SSDT), open the Integration Services project that contains the package.
Open the package in the SSIS designer.
If the Properties window does not show the properties of the package, click the design surface.
In the Properties window, in the Security group, select the appropriate value for the
ProtectionLevel property.
If you select a protection level that requires a password, enter the password as the value of the
PackagePassword property.
On the File menu, select Save Selected Items to save the modified package.
SSIS Provide different Protection levels;
    DontSaveSensitive
    EncryptSensitiveWithUserKey
    EncryptSensitiveWithPassword
    EncryptAllWithPassword
    EncryptAllWithUserKey
    ServerStorage
For better undertsnading you can use below link;
http://www.mssqltips.com/sqlservertip/2091/securing-your-ssis-packages-using-package-protection-level/
Thanks

What version of sql anywhere will run to windows 8.1

Hi, can i ask some help what version of sql anywhere that will run in windows 8.1 ?
Thank you in advance.

You can find the latest platfrom support here:
SAP SQL Anywhere Supported Platforms and Engineering Support Status
For specific patch levels required, check the link above, but basically the latest patch levels of versions 12 and 16 are supported on Windows 8.x.
--Jason

SQL Anywhere 12 (12.0.1.4155) using EF : Unable to enlist transaction; DTC may be down

What may be causing this error??
Sometimes the transactions runs fine, and other times I get this error message.
Database.SqlQuery<int>("select dba.getnextid()");
NativeError: -803
Message: Unable to enlist transaction; DTC may be down
Source: SQL Anywhere .NET Data Provider
StackTrace:
at iAnywhere.Data.SQLAnywhere.SAException.CheckException(Int32 idEx)
   at iAnywhere.Data.SQLAnywhere.DurableResourceManager.Enlist(SAInternalConnection conn, Transaction tran)
   at iAnywhere.Data.SQLAnywhere.SAInternalConnection.Enlist(Transaction tran)
   at iAnywhere.Data.SQLAnywhere.SAConnection._EnlistTransaction(Transaction tran)
   at iAnywhere.Data.SQLAnywhere.SAConnection.EnlistTransaction(Transaction transaction)
   at System.Data.EntityClient.EntityConnection.EnlistTransaction(Transaction transaction)
Can't seem to figure out how to resolve this issue, nor what's causing it.

Enabling the MSDTC service solved it. (Distributed Transaction Coordinator)

I can't open my iPhoto - tells me to use the new version

i can't open my iPhoto!
this the message that i get
"You have made changes to your photo library using a newer version of iPhoto. Please quit and use the latest version of iPhoto."
I have iPhoto 4 on my G4 at home. I tried transferring some burned photos from my G4 labtop (running on iPhoto 5) and this was the message i got. I tried everything from the update downloads to deleting the pics from iPhoto 5. I still can't open my iPhoto.
Just had a baby girl and it's driving me nuts because I can't access my photo library.
Please Help ... desperate new dad!

Hi, Gary. If the CD you burned in iPhoto 5 is still in your computer, eject it and see whether that makes any difference.
If you copied the contents of that CD to your hard drive in such a way that there is now an iPhoto Library folder anywhere on your hard drive which was created by iPhoto 5 rather than iPhoto 4, trash that folder and empty the trash. Then try opening iPhoto 4 again.
When you burn a CD from within iPhoto, it creates an iPhoto Library folder on the CD. That library folder is specific to the version of iPhoto that created it. If an older version of iPhoto finds such a folder anywhere within its reach, it tries — and fails — to open that folder instead of its own library folder, and then puts up the error message you've seen.
In the future, if you transfer photos from a computer that contains a newer version of iPhoto than your own, it will be safer to export the photos from the newer version of iPhoto to a folder on that other computer's hard drive, then burn a cd containing the photos from the Finder, rather than from within iPhoto. That way the disc won't contain anything your own version of iPhoto can mistake for its iPhoto Library.

Safe to use SQL-Anywhere Version 9?

Similar Messages

Maybe you are looking for