Hi,
Could anyone refer me any kind of tools or process to convert from SYBASE to SQL SERVER 2000.
My complany is trying to migrate from SYBASE to SQL SERVER 2000.
Any help is greately appreciated!
Thanks.
I'm having data converted to unicode and I don't understand why.
My Sybase server is configured with the standard Latin CP1252 character set and my source column is varchar(2000). My understanding is this should not be unicode in Sybase.
My SQL Server 2005 SP2 is configured with the standard SQL_Latin1_General_CP1_CI_AS collation. Again, my understanding is this should not be unicode.
I'm connecting to Sybase Adaptive Server Anywhere 9.0.2 from SSIS SP2 via the Data Reader Source using the .Net ODBC data provider.
My SQL Server destination column is a varchar(2000) column. To me, it looks like I'm going from one equivalent data type to another yet I receive the 'cannot convert between unicode and non-unicode data types' message.
Now, I can get around this in several different ways, but that's not my question. My question is: WHERE is the conversion to unicode occuring and WHY is it occuring?
I have the following SQL statement from a Sybase 5 database and I don't know how to get it to work in a SQL 7 database. Any help much appreciated.
TIA, DBA without the PAY
SELECT firms.id, firms.description, firm_mailing_addresses.firm, firm_mailing_addresses.address1, firm_mailing_addresses.address2, zip_codes_a.city as mailing_city, zip_codes_a.state as mailing_state, firm_mailing_addresses.zip_code as mailing_zip, firm_mailing_addresses.zip_plus4 as mailing_zip_plus4, firm_physical_addresses.firm, firm_physical_addresses.directory_phone, firm_physical_addresses.address1, zip_codes_b.city as physical_city, zip_codes_b.state as physical_state, firm_physical_addresses.zip_code as physical_zip, firm_physical_addresses.zip_plus4 as physical_zip_plus4 FROM {oj {oj firms LEFT OUTER JOIN firm_physical_addresses ON firms.id = firm_physical_addresses.firm} LEFT OUTER JOIN firm_mailing_addresses ON firms.id = firm_mailing_addresses.firm}, {oj firm_physical_addresses LEFT OUTER JOIN zip_codes zip_codes_b ON firm_physical_addresses.zip_code = zip_codes_b.zip_code AND firm_physical_addresses.zip_plus4 = zip_codes_b.zip_plus4}, {oj firm_mailing_addresses LEFT OUTER JOIN zip_codes zip_codes_a ON firm_mailing_addresses.zip_code = zip_codes_a.zip_code AND firm_mailing_addresses.zip_plus4 = zip_codes_a.zip_plus4} WHERE firms.id = 120
I've installed Sybase client 12.0 and have created the DSN (it is successful, connection is established) but when I run this ActiveX Script from DTS Package it give me error Data Source Name not found and no default driver specified
Dim RS Dim oConn
Set oConn = CreateObject("ADODB.Connection") msgbox "set oConn" Set RS = CreateObject("ADODB.Recordset") msgbox "RS" (I've tried both open statement in both it gives me same error) oConn.Open = "Driver={Sybase ASE ODBC Drivers};Srvr=Server1;Uid=sa;Pwd=password"
I'm trying to configure replication between a Sybase ASE Database Server and SQL Server 2000. Sybase ASE Database will be the Publisher and SQL Server will be the Subscriber. Can anyone advise me on how I can go about setting up the replication for this?
Could anyone please let me know which is the best way to Synchronise a Sybase database with a MS SQL Server 2000 database.That is , the changes made in the Sybase database should be reflected in the SQL Server database.
I have a module in power builder with Sybase database as its backend. The other modules related to the same application are running on Delphi with SQL server as backend.
My requirement is to sync between the Sybase database and SQL server (2000) in order to update the SQL server with all the transactions ( online ) done in the Sybase database.
Has anybody had any experience of this??We have over 2000 stored procs to convert from Watcom SQL to SQLServer 2000. Any automated tools would be much appreciated!!Also any known issues.
I am having an issue with a Report in SSRS against a Sybase db.
The dataset for the report is a Sybase stored proc which is passed a parameter (varchar). When I run the proc in Sybase it runs fine, when I run it in SSRS in the data tab it runs fine, but when I try to preview the report, or run from IE after deploying it I get the following error:
An error has occurred during report processing. (rsProcessingAborted) Get Online Help Query execution failed for data set 'Table_1'. (rsErrorExecutingCommand) Get Online Help The given type name was unrecognized
Looks like it is an error converting the string in SSRS to a varchar in Sybase, but I don't know how to fix it.
If I create a table with an identity (int) column and the varchar column, join this to the proc and pass the int as the parameter the report works fine!! (This is not an option in production though.)
I am using SybaseASE OLE DB Provider Version 02.70.0032
Just a quick question, does anyone know any major issues with Migrating Sybase Databases to SQL Server? Just wondering if their any oddities I should be aware of? Thanks nixies
Can anyone help me with this scenario!!!! I have a sybase database and a sqlserver 2000 database. I want to insert data into sybase database table thru sql-server 2000 using distributed queries When i execute the following the transaction
Create procedure myCurrentDataBaseProcedure as begin
begin tran insert into mytable values(1) if @@error <>0 begin rollback transaction return end insert into sybasedatabaseserver.databasename.dbo.tablename values(1) if @@error <>0 begin rollback transaction return end commit transaction end
The procedure is created in sql server database trying to execute this procedure..shows error The first part of the procedure is executed.
But the error is here insert into sybasedatabaseserver.databasename.dbo.tablename values(1) The data is succesfully inserted in the local database I am unable to insert data into the remote database Can anyone suggest me wht shd i do in this scenario Are there any drivers to be loaded to commit this transactions
I have been having tremendous trouble getting OLEDB connections to Sybase that I use within SQL Server 2000 and SQL Server 2005 to work properly - they always seem to revert to the older, third party Sybase drivers if they are installed on the machine and just generally cause problems - I have given up on using them within an SSIS package all together and gone down another route.
Can anyone confirm to me whether or not this is because the version 15 native drivers that Sybase provide are not supported by SQL Server, please?
:confused: How do I tap advanced functionality like #temptable and @var from openquery? There is a linked server from SQL Server 2000 to Sybase 12 using Sybase.ASEOLEDBProvider. Executing an openquery statement from MS SQL will retrieve Sybase data; however, I have no advanced functionality available. When I try to use temporary #tables or declare @vars it returns this error... Server: Msg 7357, Level 16, State 2, Line 1, Could not process object '…OLE DB error trace [Non-interface error: OLE DB provider unable to process object, since the object has no columnsProviderName='Sybase.ASEOLEDBProvider', Query=…
Linked Server configuration: Provider options: AllowInProcess is checked Server options: Collation Compatible, Data Access, RPC and RPC Out are checked
Does anyone have a suggestion or alternative for this functionality? Thank you very much for your input.
We plan to convert our current OLTP intensive application from Sybase on NT to SQL 2000. Which one is the winner in terms of performance. I was told that SQL Server has less tools to tune the database especially for OLTP intensive database.
Have you done any test comparing the performance between Sybase and SQL server? What is your opinion on this? Do you know any good third party tools to tune SQL 2000?
I will be migrating Sybase Databases (and Centura) to MS SQL Server Databases. While I have administered MS SQL Server for many years, I have never administrated or even saw a Sybase database. My question, can anyone suggest any books to get me up to speed on Sybase, so I can transfer all databases, including tables, procs, etc... to MS Sql Server?
I have MSDE installed on a production machine together with a bunch of ASP.NET applications. I was asked to replace MSDE with SQL Server 2000 and move every application from MSDE to SQL Server 2000 with minimum downtime.
Did any of you go through a similar process?
What is the best way of doing this conversion?
How to move the backups from MSDE to SQL Server?
Is it possible to have MSDE and SQL Server 2000 coexists for a time while moving stuff around and redirecting every connection?
Any hints or suggestions would be greatly appreciated.
hello friends, i am facing a problem in SQL Server 2005 Express Edition. The database created in the SQL Server 2005 Express is when opened in SQL Server 2000, it changes the data type of all the columns of all the table to text type. can anybody help me?
I've try to use DTS to import data from Sybase 11 database to MSSQL2000 database. After the import process completed, I found that all the Keys, triggers disappeared. How do I solve the problem???
People, help me with this? Already broke my brain.
I have some data on Sybase 9.0.2.3198, i'm tryin to render report with MSSQL ReportingServices 2000 Eval SP2.
the report designer is fyiReportDesigner 3.0 - and I can do preview with it.
after deployment I'm tryin to render it, RS gives me an error:
An error has occurred during report processing. (rsProcessingAborted) Get Online Help Query execution failed for data set 'Data'. (rsErrorExecutingCommand) Get Online Help Column '@start_date' not found
I tried connect through ODBC and OLEDB both - same result.
ps I'm gonna kill somebody real soon.
the sql:
WHERE PERIOD.BEGINDATE between CAST(@start_date as timestamp) and CAST(@end_date as timestamp)
A question that may have been asked on many occasions, but what can be advised as the best way to migrate a Sybase 11.x DB to SQL 7.0, (without using BCP). Does DTS support such migrations and if so, where in DTS can this be done? I'd appreciate any basic help here to get me started on this exercise. MAny thanks
We have Trading Applications (Equities & Portfolio written on C++) on MS SQL Server 2000. Now the management is deciding to move it on Sybase 12.5. We currently don't have any issues on any matter, but because everyone is SYbase fan here, thinks applications are critical and we need to move to Sybase. Can anyone who has worked on both knows the major pros & cons of both the system. Actually I wanted these systems to be on MS SQL Server. I need solid reasons except being cheaper than Sybase to show why we should use MS SQL Server
If anyone can share their experiences, it would be really great.
Has anyone ever experienced compatibility and/or performance issues when SQL 2K and Sybase are run concurrently on the same server? I believe the server is using Windows 2K3.
I have restored a SQL 2000 DB in a SQL 2005 server. The views which were converting a varchar to string was working fine in 2000 and in 2005 the views are giving a "error converting varchar to datetime" error.
Any ideas to rectify this issue?
Prakash.P The secret to creativity is knowing how to hide your sources!
Hi, I have a situation where in I need to insert a record in sybase database table whenever there is an update on a table in my sql server database. Can any one suggesst me hoe can I do it? thanks In advance Mohan
We have created linked servers that connect to Sybase databases using the Sybase OLE DB provider and the Sybase ODBC provider.
The OLE DB provider does not allow the execution of a stored procedure. The message sounds like a permissions issue, but the id specified in the linked server has execute priv. for the stored procedure. It also does not allow the fully qualified name <server>.<db>.<owner>.<obj> to be used.
There are other issues with OLD DB and ODBC.
Anyone have any experiences making MS SQL to Sybase work smoothly?
Cannot create an instance of OLE DB provider "ASEOLEDB" for linked server "[SERVER_NAME]"
The current setup: Our primary database is on Sybase, I needed to extract hierarchical (nested) XML from multiple tables on Sybase. Although Sybase ASE 15.5 has `FOR XML` query capability it does now allow nested XML format. So we used the 'FOR XML', XML functionality in SQL Server (as we had a SQL Server 2008 database available which is used for a smaller system) to query Sybase tables through a Linked Server connection.Our sample nested XML Format is similar to: