Has anybody had any experience of this??
We have over 2000 stored procs to convert from Watcom SQL to SQL
Server 2000. Any automated tools would be much appreciated!!
Also any known issues.
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"
oConn.Open="DSN=Test;Uid=sa;Pwd=password"
msgbox "open"
Can anyone guide me?
Thanks in advance
-Sejal
Hi all,
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?
Thanks!
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.
Hi All,
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.
Thanks in advance !!
regards,
Hari Haran Arulmozhi
Hi all,
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.
Thanks in advance ,
Hari Haran Arulmozhi
Hi all
I try to migrate sybase to SQL Server 2000, but found a los of trouble, please, some can help me to resolve this???
May many of that are easy to resolv, but is mi fist time with SQL Server 2000... plz, help :(
Object : Procedure
Error : Sintaxis incorrecta cerca de la palabra clave 'cursor'.
Code :
Create Procedure ABA_CenResul
as
Begin
declare @EST_CEN_Codigo char(8),
@EST_CEN_Descripcio char(100),
@n char(100),
@name char(100),
@salida char(8),
@vble int,
@ini int,
@ter int,
@indice int,
@aux_descripcion char(100)
declare sonido cursor
for
select EST_CEN_Codigo, EST_CEN_Descripcio
from EST_CenResul
open sonido
fetch sonido into @EST_CEN_Codigo,@EST_CEN_Descripcio
select @EST_CEN_Descripcio = @EST_CEN_Descripcio + " "
select @aux_descripcion = @EST_CEN_Descripcio
while @@sqlstatus !=2
begin
select @indice = 1
while @indice <> 4
begin
select @vble = patindex("% %",@EST_CEN_Descripcio)
select @ter = @vble - 1
select @name = substring(@EST_CEN_Descripcio,1,@ter)
if @indice = 1
select @n = @name
else
select @n = @n + "/" + @name
select @ini = @vble + 1
select @EST_CEN_Descripcio = substring(@EST_CEN_Descripcio,@ini,100)
select @indice = @indice + 1
end
print @n
exec sdxsrvr...soundex @n, @salida out
update EST_CenResul
set EST_CEN_Soundex = @salida
where EST_CEN_Codigo = @EST_CEN_Codigo
fetch sonido into @EST_CEN_Codigo, @EST_CEN_Descripcio
-- select @EST_CEN_Descripcio = @EST_CEN_Descripcio + " "
-- select @aux_descripcion = @EST_CEN_Descripcio
end
close sonido
deallocate cursor sonido
end
Thnx in advance
How can import sybase db (sql any where) to sql server 2000 ?
sybase can be imported to sql server how ?
I try to import but there is no option to import sybase db
by tool -> data transformation services -> import / export data
Regards
Mateen
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
View 2 Replies View RelatedCan 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
Pl.Help
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?
Thank you
I am currently running SQL Server 2000 Standard on my production system, and I am looking to upgrade the system to Windows 2000 Adv. Server. I would also like to upgrade SQL Server 2000 Standard to SQL Server 2000 Enterprise to utilize more than 2GB of memory. Can anyone tell me what is the best way to upgrade the system, and please provide some feedback on your experiences with the upgrade. Thanks in advance.
View 2 Replies View RelatedHi,
I'm planning an upgrade of SQL 7.0 on NT 4.0 to SQL 2000 and of course I will attempt to upgrade the OS to Windows 2000 first.
Can anyone tell me of any issues I may run across during this upgrade?
Can I assume that SQL 7.0 will run ok on Windows 2000?
thanks much,
Robert
We have 2 SQL servers in a failover cluster environment. SQL1 and SQL2. Currently SQL1 is the primary in the cluster, and we need to upgrade from Service Pack 3 to Service Pack 4.
Our setup:
Both servers are Windows 2003 Server Enterprise Edition.
Both servers have SQL Server 2000 Service Pack 3.
My question is:
Which upgrade plan do I take? Do I:
1. Upgrade the backup (offline) server in the cluster (SQL2) first, reboot, then failover from SQL1 to SQL2? Then do the other server?
2. Upgrade the primary (online) server in the cluster (SQL1) first and see if it replicates to the backup?
Any advice or tips would be most appreciated.
Thanks.
I restored a 2000 database back up in to my 2005 database and it works fine. THe only problem is that I cannot create diagrams.
I get the following message:
Database diagram support objects cannot be installed because this database does not have a valid owner. To continue, first use the Files page of the Database Properties dialog box or the ALTER AUTHORIZATION statement to set the database owner to a valid login, then add the database diagram support objects.
I have checked the db_owner and that is a valid owner.
I changed a few times to different owners and still could not install the diagrams..
Any ideas?
thanks
I have to upgrade and move SQL Server 2000 databases from a platform using Server 2000 to one running SQL Server 2005. The server nameinstances will need to be the same so that a number of third party applications and front end systems that connect, and are outside of my control, will not need any data source changes. The servers will be on the same network and can't co-exist with the same name so I guess that I have to go "big bang".
Does anyone have any suggestions for a strategy that I can use?
Does anyone know of any issues that I should be aware of?
I have run the SQL Server 2005 Upgrade Advisor and it tells me the databases should upgrade OK with a few minor issues that can be fixed after.
Thanks,
Hello all,
I'm finding the documentation online to upgrading from 2000 to 2005 fairly poor.
What are the upgrading options and which one is the best option for a web server database.
Also what are best practices pre-upgrade, during upgrade and post-upgrade.
Cannot find much online.
Also since this question will be asked often might as well make it a sticky.
Thanks
Hello
I'm trying to upgrade a Microsoft SQL 2000 (8.00.760 SP3) server to SQL 2005.
It€™s a standard install, std version, not very big databases, default instance, plenty of memory etc. OS is a 2003 server recently upgraded from 2000. All patches etc are installed.
Upgrade was going fine and had got approx 90% through, had started the 2005 db service and converted the databases before it got the following error:
SQL Server Setup could not connect to the database service for server configuration. The error was: [Microsoft][SQL Native Client]Invalid connection string attribute Refer to server error logs and setup logs for more information. For details on how to view setup logs, see "How to View Setup Log Files" in SQL Server Books Online.
The 'For help' link returned the helpful... €˜We are sorry but we can€™t help€™...
Worked through http://msdn2.microsoft.com/en-us/library/ms143698.aspx but not 100% applicable and didn€™t resolve.
Partially rolled back, rebooted and resumed install but failed in the same place. Ended going back to a backup snapshot so is now back running as SQL 2000.
Excerpt from install log is below...
Thanks in advance for any assistance.
<Finished SQL statement: Wed Oct 10 21:25:21 2007>
<Started SQL statement: Wed Oct 10 21:25:21 2007> BEGIN DECLARE @GroupName AS nvarchar(4000) SET @GroupName = QUOTENAME(N'PROPMAN-DATASQLServer2005MSFTEUser$PROPMAN-DATA$MSSQLSERVER') EXECUTE(N'grant execute on sp_fulltext_getdata to ' + @GroupName) END
<Finished SQL statement: Wed Oct 10 21:25:22 2007>
Service MSSQLSERVER is being stopped at Wed Oct 10 21:25:22 2007
Service MSSQLSERVER with parameters '' is being started at Wed Oct 10 21:25:34 2007
Attempt to start service when it is already running
SQL service MSSQLSERVER started successfully waiting for SQL service to accept client connections
Service MSSQLSERVER started at Wed Oct 10 21:25:40 2007
<EndServerDowntime Wed Oct 10 21:25:40 2007>
Loaded DLL:
C:WINNTsystem32Odbc32.dll
Version:
3.526.3959.0
SQL_ERROR (-1) in OdbcConnection::connect
sqlstate=01S00, level=-1, state=-1, native_error=0, msg=[Microsoft][SQL Native Client]Invalid connection string attribute
Error Code: 0x8007ea62 (60002)
Windows Error Text: Source File Name: libodbc_connection.cpp
Compiler Timestamp: Fri Jul 29 01:13:53 2005
Function Name: OdbcConnection::connect@upgradeconnect
Source Line Number: 148
---- Context -----------------------------------------------
sqls:equenceInstaller::launchAction
Staring action SqlScript
SqlUpgradeScriptHlpr
Connecting to SQL Server
ExecuteUpgradeSqlCommands
sqlConnect
Originial error was 8007ea62 (60002)
Error Code: 60002
MSI (s) (5C!20) [21:26:20:164]: PROPERTY CHANGE: Adding SqlUpgradeMessage property. Its value is 'SQL Server Setup could not connect to the database service for server configuration. The error was: [Microsoft][SQL Native Client]Invalid connection string attribute Refer to server error logs and setup logs for more information. For details on how to view setup logs, see "How to View Setup Log Files" in SQL Server Books Online.'.
SQL Server Setup could not connect to the database service for server configuration. The error was: [Microsoft][SQL Native Client]Invalid connection string attribute Refer to server error logs and setup logs for more information. For details on how to view setup logs, see "How to View Setup Log Files" in SQL Server Books Online.
Loaded DLL:
C:WINNTsystem32Odbc32.dll
Version:
3.526.3959.0
SQL_ERROR (-1) in OdbcConnection::connect
sqlstate=01S00, level=-1, state=-1, native_error=0, msg=[Microsoft][SQL Native Client]Invalid connection string attribute
Error Code: 0x8007ea62 (60002)
Windows Error Text: Source File Name: libodbc_connection.cpp
Compiler Timestamp: Fri Jul 29 01:13:53 2005
Function Name: OdbcConnection::connect@upgradeconnect
Source Line Number: 148
---- Context -----------------------------------------------
: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 shall be taking a bunch of 7.0 instances and moving/upgrading to a SQL 2000 cluster server. I was thinking of creating new named instances on the 2000 cluster and upgrading each 7.0 server to it's respective named instance. Also thought of using the 2000 copy database wizard; I was told this didn't always work. Anyone hear of problems with this?
Thanks
I recently upgraded from SQL Server 2000 to SQL Server 2005. I have Oracle databases I need to share data with. I was using the Heterogeneous Services (hsodbc) from Oracle and connected to SS 2000 fine. Since I've upgraded, I can't use hsodbc to connect to my SS 2005 database. I get the following error:
ORACLE GENERIC GATEWAY Log File Started at 2006-09-06T09:40:07
hoainit (3): ; hoainit Exited with retcode = 0.
hoalgon (7): ; hoalgon Entered. name = edw.
DB_ODBC_INTERFACE (2085): ; [Microsoft][SQL Native Client][SQL Server]Login
failed for user 'edw'. (SQL State: 28000; SQL Code: 18456)
DRV_InitTdp: DB_ODBC_INTERFACE (2085): ; [Microsoft][SQL Native Client][SQL
Server]Login failed for user 'edw'. (SQL State: 28000; SQL Code: 18456)
nvRETURN (F:WorkConnect_4_6_3srcdrvDRV_BIND.C 356): -2220
nvRETURN (F:WorkConnect_4_6_3srcavNAV_BIND.C 293): -2220
hoalgon (7): ; hoalgon Exited with retcode = 28500.
My upgrade of SQL Server 2000 to SQL Server 2005 is being blocked as follows:
Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding
FTCATALOGPATH
DEPRECATEDSP
FTCATALOGNAMERESTRICTION
FTNONPERSISTEDCOMPCOL
Many thanks
JMX
Hi,
We just upgraded 2 sql servers from sql server 2000 sp3a to sql server 2005 build 2153, and merge rep exists between these 2 servers.
However, after sql server upgrade, we had to reinitialize merge replication and now the merge agent is reporting 2 errors
1)
Error messages:
The Merge Agent failed to upgrade triggers, metadata and stored procedures on the Subscriber to versions compatible with SQL Server 2005. Restart synchronization, and if this failure continues to occur reinitialize the subscription. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147199403)
Get help: http://help/MSSQL_REPL-2147199403
Invalid column name 'metadata_select_proc'. (Source: MSSQLServer, Error number: 207)
Get help: http://help/207
Invalid column name 'delete_proc'. (Source: MSSQLServer, Error number: 207)
Get help: http://help/207
2)
Command attempted:
{call sp_MSensure_single_instance (N'Merge Agent Name', 4)}
Error messages:
The merge process could not connect to the Publisher 'Server:database'. Check to ensure that the server is running. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147199368)
Get help: http://help/MSSQL_REPL-2147199368
Another merge agent for the subscription(s) is running or the server is working on a previous request by the same agent. (Source: MSSQLServer, Error number: 21036)
Get help: http://help/21036
looking inside the sp_MSensure_single_instance stored procedure, it's trying to obtain an exclusive lock on resource 'Merge Agent Name' but fails and returns -1
this is the stored procedure executed by sp_MSensure_single_instance and @retcode = -1 and thus cannot obtain exclusive lock on resource
EXEC @retcode = sys.sp_getapplock @Resource = 'Merge Agent Name',
@LockMode = 'Exclusive',
@LockOwner = 'Session',
@LockTimeout = 0,
@DbPrincipal = 'MSmerge_PAL_role'
so i think it's failing because for some reason MSmerge_PAL_role database role does not have enough rights to obtain exclusive lock on necessary resources
i've tried many things to fix this, including scripting out and dropping all merge rep, turning off replication db option and reapplying replication create scripts on the server, and even manually deleting the MSmerge_PAL_role database role but still doesn't work
can anyone help?
Thanks
Hi All,
I had two Window NT 4.0 Server, say A and B... We recently upgraded from MS SQL Server 6.5 to MS SQL Server 2000 on Computer A, and for Computer B, I installed SQL Server 2000 from scratch. These two have a same RAM(512MB) and CPU speed...so the setup for hardware is almost identical...
For server A, there are around 10 connection to this SQL Server...
For server B, there are also around 10 connection to this SQL Server...
The database for SQL Server B is a copy from SQL Server A.... I restored the database on SQL Server B from the backup dump of Server A...
We have a store procedure called usp_GetMemo(ID Interger) ... we feed ID number to this store procedure and return its return Description... this table has ID column and it's Non-Cluster index, allow the duplicate row... there are 1.7 million records for this table...
Here is problem... whenever i execute more than 100 times for this store procedure(usp_GetMemo(ID)) continuously, the CPU usage of Computer A is 3 times bigger than computer B....
I did run the command "DBCC DBReindex" , "Update Statistics" for this table on computer A, but did not make any difference...
Keep in mind that Computer A has been upgraded to SQL server 2000 while Computer B installed from scratch... would that make difference somehow?? Before the upgrading, the CPU usage of computer A is the same as Computer B...
Any help will be really appreciated,
Thanks alot,
Kim,
I don't have any idea about upgrading databases.I am been given this task.
It would be great if you let me know what are all the things to be considered upgrading the sql server 2000 databases to sql server 2005.
Please let me know
Thanks
Is it just me, or are features missing in Management Studio? I mean, where is the "Export Objects" option when exporting data? Why is it so difficult to register a remote server? Why do the object views suck? And most important, why is the documentation the worst software documentation I have EVER SEEN?!
Things that were easy in Enterprise Manager with Client Network Utility and Query Analyzer seem impossible, difficult, or maybe just hidden in Management Studio. If it is there, the documentation sure doesnt tell you how to find it.
Please someone tell me that it's just me. Tell me that the features are there but Im not doing something right. I feel like putting my head in between my door opening and banging the door against it.
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?
Thanks!
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?
Bill
I am trying to run the SQL Server 2000-Switch application to upgrade my 6.5 database to SQL2000. The error I am recieving is error 8344, which on Microsoft website, states : Insufficient access rights to perform the operation. I have checked all of the rights on the servers. Microsoft states that each SQL Server service account must have a domain account logon, and it does, and the service account on the box must be a local admin on the box, and that it is. What happens is I select the export and import server and then it stops and starts services, and then returns to the exact login page.
Any suggestions????
Thanks
Hi, I am working on upgrading SQL Server 6.5 databases to SQL Server 2000 to a new server. I was not able to find details documents on that. Can anyone give me some ideas?
View 1 Replies View Related
Hi,
I would like to find out if there is any way to upgrade SQL Server 2000 (Ent) to 2005 (STD)
The Instance has many logins and jobs etc and I dont want to loose those
A document or some advice on how to go about it would help
Thanks
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???
Kung Wu
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)
these are the RDL-file pieces:
<QueryParameters>
<QueryParameter Name="@start_date">
<Value>=Parameters!start.Value</Value>
</QueryParameter>
<QueryParameter Name="@end_date">
<Value>=Parameters!end.Value</Value>
</QueryParameter>
</QueryParameters>
<ReportParameters>
<ReportParameter Name="start">
<DataType>String</DataType>
<DefaultValue>
<Values>
<Value>2007-08-15</Value>
</Values>
</DefaultValue>
<Nullable>false</Nullable>
<AllowBlank>false</AllowBlank>
<MultiValue>false</MultiValue>
<Prompt>Start</Prompt>
</ReportParameter>
<ReportParameter Name="end">
<DataType>String</DataType>
<DefaultValue>
<Values>
<Value>2007-08-15</Value>
</Values>
</DefaultValue>
<Nullable>false</Nullable>
<AllowBlank>false</AllowBlank>
<MultiValue>false</MultiValue>
<Prompt>End</Prompt>
</ReportParameter>
</ReportParameters>