Hi recently i moved sybase 8.0 database to mssql server 2000,here i actually got problems after done megration we tested some quaries and stored procedures they are running very long among that one quary is running like 6 hours priviously it was running on sybase server for 45 minutes what would be the major blow for this problem SRJ2005
Ok, how about the database optimization tasks such as reindexing and re-compiling the stored procedures, that will give more length to performance gain in case of SQL server. Satya SKJ Microsoft SQL Server MVP Contributing Editor & Forums Moderator http://www.SQL-Server-Performance.Com This posting is provided AS IS with no rights for the sake of knowledge sharing.
See if this helps: http://www.microsoft.com/resources/documentation/sql/2000/all/reskit/en-us/part2/c0661.mspx http://www.microsoft.com/technet/itsolutions/migration/unix/sybsqlsv/default.mspx If not, please post the query in question. -- Frank Kalis Moderator Microsoft SQL Server MVP Webmaster:http://www.insidesql.de
So as this sorted out now with the recompile? Satya SKJ Microsoft SQL Server MVP Contributing Editor & Forums Moderator http://www.SQL-Server-Performance.Com This posting is provided AS IS with no rights for the sake of knowledge sharing.
wasn't sybase 10 or 11 contemporary with SQL 7, so sybase 8 would probably be comparable to SQL 6 in which case i would think the issue is more likely to be with the change from a basic optimizer to the cost based optimizer in s2k even oracle had huge problems with cbo that many people stuck to rules, until the more recent versions. i would look the exection plan, run the query with SET STATISTICS PROFILE ON then look for expensive ops that probably should not be also SET STATISTICS IO ON SET STATISTICS TIME ON exec -- query for the plan copy the plan info to excel, for the IO and TIME, copy the messages to a text file