Query Runs On Sql7.0 But Keeps Running On Sql2000 Without Output
Aug 15, 2001
The following query runs fine on sql 7.0 but it kind of hangs/keeps running without any output on sql server 2000
---------------------
Set @cmd = 'Update ABCD Set
'+@day+'_LB = IsNull(LB,0),
'+@day+'_UT = IsNull(UNIT,0)
From tempData as T
Where T.STORE_NUM = ABCD.STORE_NUM And T.ITM_ID = ABCD.UPC'
execute (@cmd)
------------------------------------
But if we hard code the @day parameter and run the query like this it runs very fast on sql 2000....
Update ABCD Set THIRD_LB = IsNull(LB,0),
THIRD_UT = IsNull(UNIT,0)
From tempData as T
Where T.STORE_NUM = ABCD.STORE_NUM And T.ITM_ID = ABCD.UPC
------------------------------
I have a very complex Stored Procedure called by a Job that is Scheduled to run every night. It's execution takes sometimes 1 or 2 hours and sometimes 7 hours or more.
So, if it is running for more than 4 hours I stop the Job and I run the procedure from a Query Window and it never takes more than 2 hours.
Can anyone help me identify the problem ? I want to run from the Job and not to worry about it.
Some more information: - It is SQL 2000 Enterprise with SP4 in a Cluster (It happens the same way in any node). - The SQL Server and SQL Agent services run using a Domain Account that have full Administrative access. - When I connect to a Query Window I also use a Windows Account.
- There is no locks or process bloking or being blocked while the job is running. - Using the Task Manager the processor activity is ok, no more than 30 % in any processor.
Can anyone point me to a white paper/discussion on the issues of gaining access to SQL2000 data from a SQL7 installation? I'm about to upgrade servers from 7 to 2000, but a few of the servers exchange data bi-directionally and the upgrade to both servers at the same time would be problematic; thus the need at some point to get at the SQL2000 data from the SQL7 server.
I'm currently on a project that'll move all my SQL7 databases into SQL2000. This is from a SQL7 production box to a new Windows2k SQL2000 box. I'm confused as to the proper way of moving all the objects over. What should i do? Any information. Thank You!
Is it possible to administer both SQL7 & SQL2000 databases from the same console ?? It's fine administering SQL 6.5 & SQL7, as 6.5 had no MMC, but it seems that SQL7 & SQL2000 have the same MMC.
Hi there, I need to create a copy of a SQL 2000 database in another server which has SQL 7.0 installed. When I do a backup and restore, it gives me the following error :
Server: Msg 3154, Level 16, State 2, Line 1 The backup set holds a backup of a database other than the existing 'inventmast' database. Server: Msg 3013, Level 16, State 1, Line 1 RESTORE DATABASE is terminating abnormally.
It seems to be like a downward compatability issue. Is there any other way to restore a sql2000 db onto sql 7 ?? Thanks Paul
I'm upgrading a set of databases from SQL7 on one server (A) to SQL2000 on another server (B). I'd like input on the best method for moving the databases over (BCP, restore from BAK, etc), and in particular on moving the list of valid users (with default databases, permissions to databases, etc) and the DTS packages and Agent jobs.
When moving the databases, which are currently in code page 850, I might want to have them convert to the standard Latin-1 of SQL2000, though this isn't critical.
I have table with about 2 million rows. Everyday about 18000 rows are inserted. The table contain events for site security system so archiving is neccessary. I would appreicate any help or ideas. Thanks in advance.
I have a SQL Server 2000 box running two databases which was upgraded in error from SQL7.0 Basically we are no longer being given support as SQL2000 is not supported by the suppliers.
I therefore need to downgrade the box to SQL7.0 and was wondering if anyone had any opinions on the best method for doing this. Note that I do have a spare server to host the databases while I rebuild this server ( I am having to do a complete rebuild from scratch for other reasons ).
My thought is to transfer the databases to the spare server, rebuild the first box to SQL 7.0 and then perform a snapshot replication to transfer the data back.
Any thoughts on this would be gratefully received.
I have a backup of a SQL7 DB that i need to restore into SQL 2000. I only have the backup of the DB , i don't have access to the SQL7 server. When ever I try to restore the DB into SQL2000 nothing works, the tables and properties all restore properly and the data is there but i can't retrieve info from it. I'm trying to move a website DB from SQL7 to SQL 2000 for use with Cold Fusion. I know they're is issues with going from 7 to 2000 but i don't know what they are. If anyone could help me with this i would greatly appreciate it. I know I need to do some special steps or changes before it will work in 2000, does anyone know what these are?
Hi, guys - looking for a bit of help/advice on moving a database fromSQL 7 to SQL 2000.We've a third party application which currently uses a SQL7 database.This database has a number of views which are owned by userINFORMATION_SCHEMA and are set as system tables. This user doesn'tactually have a login on the SQL server.We've tried the following to recreate the database on SQL2000, butwhatever we try, the views owned by INFORMATION_SCHEMA won't copy overfrom SQL7:(1) We tried the "Copy Database" wizard in SQL2000, but were gettingerrors when trying to actually copy the database (other steps workedfine).(2) We tried a restore to SQL2000 from our Legato Networker backup ofthe SQL7 database, but the views didn't come across.(3) We tried a backup from SQL7 and restore to SQL2000, but got themessage that the backup file contained a database other than the onewe wanted (it didn't - we checked the backup file several times byrestoring it to another SQL7 server).(4) We tried to import/export data from SQL7 to SQL2000, but the viewsowned by INFORMATION_SCHEMA weren't showing to add to the list ofobjects to take across.(5) We created the INFORMATION_SCHEMA login on SQL2000, and tried allrestores again, but still the views wouldn't go across.(6) We generated the SQL for all views in SQL7 and ran these onSQL2000, setting the owner to INFORMATION_SCHEMA, but wasn't surewhere to set the type to "system" (as opposed to "user).We're having problems running the third party application with aconnection to SQL2000, and want to rule out the lack of views, or viewownership, as the problem. Our third party vendor isn't coming upwith any solution in a hurry. Can anyone think of any reason why theviews are coming across when the database is restored to SQL2000?Thanks for your help.
I have setup SQL2000 Personal edition on my notebook.
I cannot connect to an existing SQL7 server on the network anymore. I used to run SQL7 Desktop edition which ran just fine. I also noticed that when I start my machine it take about 2 minutes until the SQL service is started.
Can anyone tell me of an EASY way to migrate a a database from a SQL 7 server to a SQL 2000 server (two different machines)?
Everything that I have found is only for upgrading SQL 7 to SQL 2000 and this isn't what I need.
Two groups in our company merged into one. The first group has a SQL 7 server that the lease is about to expire on and the second group (mine) has a newer SQL 2000 server that we need to move all of the databases to.
I have tried DTS. It failed. I tried backing up the 7 server and restoring to the new server. It failed.
I'm attemting to replicate from a SQL7 box to SQL2000.
The snapshot works fine, but it fails when it tries to push the subscription to the SQL2000 box with a trust error (I don't recall the exact message). I noticed that it fails when Enterprise Mgr is configured as: "Tools/Replication/Configure Publishing, Subscribers and Distribution", Subscriber Tab, "Impersonating SQL Service Agent". It works if I change to "SA".
This is only the case when we replicate from SQL7 to SQL2K. SQL7 to SQL7 works fine with "Impersonating". Has anybody seen this behavior? Any workarounds, other than using SA?
Im using MS SQL7 as database software ,but now I plan to upgrate SQL7 to SQL2000 . I would like to know that are there any affect on the old database that already use with sql7 after I upgrade to MSSQL2000 ?
I'm attemting to replicate from a SQL7 box to SQL2000.
The snapshot works fine, but it fails when it tries to push the subscription to the SQL2000 box with a trust error (I don't recall the exact message). I noticed that it fails when Enterprise Mgr is configured as: "Tools/Replication/Configure Publishing, Subscribers and Distribution", Subscriber Tab, "Impersonating SQL Service Agent". It works if I change to "SA".
This is only the case when we replicate from SQL7 to SQL2K. SQL7 to SQL7 works fine with "Impersonating". Has anybody seen this behavior? Any workarounds, other than using SA?
Current system 2 x 500mhz pIII 512MB ram, System mirrored and data raid 5 30GB made from 3 disks. All server is running in CA TNG. an Asset management DB and Software Delivery database. But the poor server runns most of the time at 100% 65% being used by SqlServer process. Does/Can anyone recommend any tweaks upgrades that may let the server take a breath in and out ie will more memory speed thing up faster processors or more disk.
Hi. I've got a report with 4 different sections - the datasets coming from some tables that are populated via a stored procedure. I'd love it if the the first thing this report did was run that stored procedure and then the data would be available for the actual reporting piece. Is that possible? And if so, how do I make it work?
Jobs not running within SQL Server Agent on SQL7 despite being schedulled. The only explanation I can think of for causing this is due to a date correction on the NT Server ( backwards ) by the NT Administrator. I can run jobs manually, but the scheduled run times are being ignored.
I'm hoping that the jobs will start running again as schedulled when the system catches up to the date it was previously at.
Has anyone had experiences of this and found a way to get things running again ?
I am experimenting with the FOR XML AUTO clause in SQL2000, but instead of nicely structured XML I get one continuous string oftags that can't be parsed by IE5.5
The BOL seem to indicate just running the query in Query Analyser will produce nicely formatted XML output - can anybody tell me what is wrong?
We are running SQL 7 on a Windows NT Server. If you copy a 25Mb filefrom this machine to a W2K server, the file copy takes over 5 minuteson a 100Mpbs switched network.Copying the same file to another NT server takes only seconds, andcopying the same file to the W2K server from the 2nd NT server, (whichis not running SQL) takes only seconds also.Has anyone any ideas as to why file copying between this machine and aW2K one will take so long. It is repliacted on 5 further w2K machines.
Here below is the perfect query i made which is working fine and giving me the sql output but just only need is how to convert to excel and automate the job scheduling so that it run on everyday and send the mail with attachment .
SELECT DN, cn, displayName, mail, objectClass, sAMAccountName, Company, givenName, sn FROM ( SELECT DN, cn, displayName, mail, objectClass, sAMAccountName, Company, givenName, sn, 1 [ordering] FROM alpha.dbo.DCADFeed where sAMAccountName collate SQL_Latin1_General_CP1_CI_AS in
I have simple query which creates tables by passing database name as parameter from a parameter table .
SP1 --> creates databases and calls SP2--> which creates tables . I can run it fine via SSMS but when I run it using SSIS it fails with below error .The issue gets more interesting when it fails randomly on some database creation and some creates just fine .
Note** I am not passing any database of name '20'
Exception handler error :
ERROR :: 615 :: Could not find database ID 20, name '20'. The database may be offline. Wait a few minutes and try again. ---------------------------------------------------------------------------------------------------- SPID: 111 Origin: SQL Stored Procedure (SP1) ---------------------------------------------------------------------------------------------------- Could not find database ID 20, name '20'. The database may be offline. Wait a few minutes and try again. ----------------------------------------------------------------------------------------------------
Error in SSIS
[Execute SQL Task] Error: Executing the query "EXEC SP1" failed with the following error: "Error severity levels greater than 18 can only be specified by members of the sysadmin role, using the WITH LOG option.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.I have sysadmin permission .
