Is anyone has an experience with choosing between MS SQL7 (or 6.5) on NT Server box and Sybase on Unix (UnixWare 2) box to use this server as WEB server? Could you tell just a couple of advantages and disadvantages of each of those systems, or to point me at the source of useful for this compare information. Any help is very appreciated. Thanks
Hi,I'm using Sybase driver under Linux and I'm trying to connect to MSSQLserver 2000.But unfortunately connection fails.In Event Log on my Win 2k3 SBS I'm getting the following error message:Error: 17832, Severity: 20, State: 7Connection opened but invalid login packet(s) sent. Connection closed.For more information, see Help and Support Center athttp://go.microsoft.com/fwlink/events.asp.I tried to update SQL server to the lastest version; currently I'm using SP4but it still didn't resolve the problem.Has anyone got an idea what may be wrong?Application is written in perl, using DBD::SybaseThanks,Martin
I got a big problem. I try to run a query on ms query analyzer or my .net-app, but in both cause, it wouldn't work. when i run the query in ms query analyzer it returns me this error-message:
Der aktuelle Zeilenwert der [verkauf_online]..[hs].[std_ftext].text-Spalte konnte nicht vom OLE DB-Provider 'MSDASQL' gelesen werden. [OLE/DB provider returned message: Die angeforderte Konvertierung wird nicht unterstützt.] OLE DB-Fehlertrace [OLE/DB Provider 'MSDASQL' IRowset::GetData returned 0x80040e1d].
sorry, its in german, i know but the most important fact is, that a conversion failed. i tried to read a text-field from a sybase asa-8-database which is linked with a ms sql-server 2000. I tried to find out more about the error-messe an the error-code (x80040e1d) but i couldn't find anything helpful.
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???
Here i had a task to migrate sybase 8.0 database to mssqlserver 2005 .how can i migrate this using INTEGRATED SERVICES (SSIS) or any other options. .Please try to provide some basical info because i am new to sybase versions.
How many result-rows does mssql return should be used asynchronous method to use mssql cursor, can get the best performance in any time in any result offset?
i want to make the cursor fast in any time whatever how many results returned
i was planning to create a database migration tool .. its a certain database of a DMS (document management system) to another DMS (two different DMS)... from DMS using msde 2000 server .. and tranfer to a DMS using a postgre sql or mssql .. depends ..
they have different table structures and names . . :D
i was thing of what language shall i use.. or what language is the best to work on this kind of project :)
Does enabling/disabling Data Execution Prevention have a performanceimpact on SQL 2000 or SQL 2005?For SQL best performance - how should I configure for:Processor Scheduling:Programs or Background servicesMemory Usage:Programs or System Cache
I am a bit new to the MSSQL server. In our application, we use so many SQL queries. To imporve the performance, we used the Database enigine Tuning tool to create the indexes. The older version of the application supports MSSQL 2000 also. To re-create these new indexes, I have an issue in running these "CREATE INDEX" commands as the statements generated for index creation are done in MSSQL 2005. The statements include "INCLUDES" keyword which is supported in MSSQL 2005 but not in MSSQL 2000.
Ex:-
CREATE INDEX IND_001_PPM_PA ON PPM_PROCESS_ACTIVITY
I am currently work on mssql 6.5. On my workstation, I have mssql 6.5 cient software.
However, I would like to install mssql 7.0 server on my nt workstation and work with it to become familiar with 7.0. Can I install mssql 7.0 server on my nt workstation? Can mssql 6.5 client coexist with mssql 7.0 on the same machine if they are in different directories?
Ben writes "I have a sql script that doesn't function very well when it's executed on a SQL 2000 server.
The scrpt looks like this:
--------------------------------------------------------------------------------------------------- USE [master] GO IF NOT EXISTS (SELECT * FROM master.dbo.syslogins WHERE loginname = N'SSDBUSERNAME') EXEC sp_addlogin N'SSDBUSERNAME', N'SSDBPASSWORD' GO GRANT ADMINISTER BULK OPERATIONS TO [SSDBUSERNAME] GO GRANT AUTHENTICATE SERVER TO [SSDBUSERNAME] GO GRANT CONNECT SQL TO [SSDBUSERNAME] GO GRANT CONTROL SERVER TO [SSDBUSERNAME] GO GRANT CREATE ANY DATABASE TO [SSDBUSERNAME] GO USE [master] GO If EXISTS (Select * FROM master.dbo.syslogins WHERE loginname = N'SSDBUSERNAME') ALTER LOGIN [SSDBUSERNAME] WITH PASSWORD=N'SSDBPASSWORD' GO GRANT ADMINISTER BULK OPERATIONS TO [SSDBUSERNAME] GO GRANT AUTHENTICATE SERVER TO [SSDBUSERNAME] GO GRANT CONNECT SQL TO [SSDBUSERNAME] GO GRANT CONTROL SERVER TO [SSDBUSERNAME] GO GRANT CREATE ANY DATABASE TO [SSDBUSERNAME] GO USE [master] GO IF EXISTS (select * from dbo.sysdatabases where name = 'ISIZ') DROP DATABASE [ISIZ] GO USE [SurveyData] GO exec sp_adduser 'SSDBUSERNAME' GRANT INSERT, UPDATE, SELECT, DELETE TO SSDBUSERNAME GO USE [SurveyManagement] GO exec sp_adduser 'SSDBUSERNAME' GRANT INSERT, UPDATE, SELECT, DELETE TO SSDBUSERNAME ---------------------------------------------------------------
I need to be converted to a script that can be executed on both MSSQL 2000 and MSSQL 2005.
I was wondering if somebody there could help me with this problem?!
I've been tasked to move our production databases on MSSQL 2000 to 2005. I've supported MSSQL since version 6.5 and performed migrations to successor versions.
Current Environment is MSSQL 2000 32-bit with current Service Packs.
I've performed mock migrations on Test servers upgrading all Production instances simultaneously from MSSQL 2000 to 2005 32-bit. The Test environment is identical to Production minus server name, IP etc. Also I have a separate server with MSSQL 2005 installed where I use the DETACH / ATTACH and BACKUP / RESTORE method for migration / acceptance testing. There are approximately 30 databases totaling 70 GB. This has gone as expected and fairly successful. Vendors have been coordinated with to update code and staff for acceptance testing.
I'd prefer going directly to MSSQL 2005 64-bit instead if possible due to memory benefits etc. This is where I'd like some feedback prior to borrowing a 64-bit server for testing.
Upgrade options:
1. Is it better to migrate from MSSQL 2000 32-bit to 2005 64-bit via: a. DETACH / ATTACH b. BACKUP / RESTORE c. Is one method more advantageous relating to the end result? 2. Regarding XP clients, have issues been experienced with the default SQL Server driver or is an alternate recommended for XP clients to connect to a MSSQL 64-bit server databases? 3. If you have performed this migration and have relevant experience please pass them along.
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 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?
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.
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 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?
Good day.I have dts running every 10 minutes in a server of slqserver 2000 who is in a country and that it sends data to another country which has a data base sybase12.5.The problem is when by reasons for the WAN the connection fails from a country to another one the dts or job fails executing its processes and I must soon give click to stop and start so that it continues. That I can do so that when the connection is lost and i need to dts reconected automatically and is continued its processing? thanks and sorry my english :)
If I need to have SQL Server be able to query a Sybase database on another machine (Adaptive Server anywhere 7.0.2 with an ODBC connection), what is the simplest, least expensive way to do this ? Thanks
Coming from Sybase env. I would like to know the equivalent of sp_showplan. What it does is, it shows the showplan for the query being run by spid, which is passed as a parameter to sp_showplan.
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.
My tribe is creating a central database, running Sybase 5 and Eaglesun. I’m curies if anyone has worked with Eaglesun and if you had any issues with the software or with data conversion??
Thanks for the input
US Navy - We are fueled, armed, and go for launch.
I am not sure is this the right forum to get solution to my question.
From where i can get sysbase basics. I am posting this query in this forum coz this forum and gurus in this forum had helped me in lot critical situtions.
I know sql and Dataware housing.I got a job offering for sybase sql but I don't anything about sybase.Will it be in programming in Actually what we will do in sybase? What will be the nature of work? and I just want to know what type of question will be asked ? Please do reply.
I am assuming someone has had success connecting to Sybase from SSIS. I am having trouble. And I freely admit naivety when it comes to something like this. :-)
I installed dbConnector 6.01 which has a Sybase connector as a part of the package. I then tried to create a connection manager for Sybase using OleDb, but it was not an option in the list of OleDb connections. So, am I correct in assuming that I need to use ODBC? If so, is there an OleDb Sybase driver that can be used with SSIS?
Any help in using SSIS to connect to Sybase would be appreciated.
It's all well and good that Microsoft has finally entered the well-established mobile database market (the market that iAnywhere Solution's SQL Anywhere product current *owns* by a wide margin). However, it should be noted that "SQL Everywhere" is a Sybase trademark. For confirmation of this fact, see http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.help.mro12.6.mro126ig/html/mro126ig/legal.htm
For confirmation of the fact that SQL Anywhere owns the mobile database market, note that it is the database of choice for the 500,000 mobile devices that will be used in the 2010 US Census; see http://www.internetadsales.com/modules/news/article.php?storyid=7347
