We are internally upgrading all of our SQL boxes to SQL Server 2005. Unfortunately our web production SQL box is hosted externally at a hosting company and it will be staying as a SQL server 2000 box. Can the new ssis wizards/functionality update tables on a sql 2000 box or a better question what would be the best way to update data (not necessarily copy whole tables) from a 2005 db to a 2000 db?
Does anybody know of a way to rollback SQL Server 2005 databases back to SQL Server 2000? Is there a way of doing it without resorting to Copy Database Wizard? I love to find a way of attaching a SS 2005 database to a SS 2000 instance without any issues.
I recently upgraded to SS 2005 and I am very unhappy with the SS 2005 and I want to rollback to SS 2000, which was a lot more stable. I am having several major issues that are affecting my whole company's day-to-day operations and the managers are not happy. Some of the issues include night time batch running very sluggish for no apparent reason. This is a biggest problem because it only occurs once or so a week and causes a disturbance with the daily activities when the night time processing isnt completed on time. The rest of the time, the batch processing runs great, even a little better then on SS 2000. I don't believe it is a matter of my application needing to be retuned because if that was the case, then why isn't it running sluggish every night? Also, it's never the same day that the sluggish behavior occurs. If it was occurring on the same night, then I would have something to investigate within our application, but it doesn't. Another issue that I am having involves a night time job that restores a copy of the production database to the Data Warehouse server to be used for updating the data warehouse. Again, most of the time it runs great (~2 1/2 hours), but once or twice a week, it goes stupid and takes 6 1/2 hours for no apparent reason. Again, it is not happening the same day either, which could give me something to invesigate. On SS 2000, this same job ran flawlessly. Never I did I run into situation that the database restoration took that long to run. Even another issue involves a SQL Server Agent Job that was put into suspended state. What's a suspended state and how can I get it out of suspended state? I can find no information about suspended state in BOL. I did a Google and nothing came up. If this suspended state was put in for security reasons, great, but then tell me how I can remove the suspended state. I am also not happy with the fact that I can't get accurate information about the queries that are actively running at that particular moment. In SS 2000, when I noticed high CPU usage on the server, I would run the sp_who2 active stored proc and it would show me all the active thread and how much CPU it was consuming. I would then find the running threads with the highest CPU numbers and investigate the query and see if we could improve it. Now in SS 2005, I get in the same situation and run the sp_who2 stored proc, and there is no smoking gun. All of the active threads are showing very little CPU usage, which I am very suspect of. What the heck happen to sp_who2? I looked at some of the other ways of looking at running processes (i.e... sys.sysprocesses) and they don't appear to be giving the information that I need.
I am very unhappy and I just want to roll back to SS 2000 and wait a couple of years before I upgrade to SS 2005.
many of us has been upgradeing from sql server 2000 to 2005 and they were using many ways to tell them what thing s are going to chaneg in thier database but if i want to downgrade from 2005 to 2000 what things are going to change in my database??????????/
I had an issue where my database was transfered from a SQL 2000 database to a SQL 2005 database.
The SQL 2005 database works fine, but my development environment is SQL 2000.
So I created a new SQL 2000 database and used the SQL 2005 DTS wizard to transfer the data. As far as I can tell, everything went fine, and the DTS wizard showed no errors.
However, when I changed my website application's connection string to the new database, the application (LaGarde StoreFront 6.0) throws a licensing error. When I checked with LaGarde, they said that it was a permissions issue, that the permissions on the database where incorrect.
I never really heard of that, but have no way to check. I really need to transfer this database back to 2000. Any help?
I've developed a web application and to be honest I've been a bit dumb and not checked with my hosts. I assumed they used SQL Server 2005. But no, they only use 2000.
I'm sure I'll come across more problems but the first I'm having is I've used the ROW_NUMBER() function in a few stored procedures, but in 2000 I'm getting this error message
'ROW_NUMBER' is not a recognized function name.
Here is the stored procedure for reference
SELECT RowNum FROM ( SELECT id, category, ROW_NUMBER() OVER(ORDER BY id) as RowNum FROM custrecords ) as CustRecord
I am maintaining a .net 1.0 asp.net web application that accesses a SQL server 2000 database. I need to backup the database and then restore it on a laptop. Currently it resides on a server. The problem is that on the server they are using sql server 2005. If I backup using 2005 and then try and restore this database using SQL server 2000 or 2005 on the laptop, I get an error message. "Too many backup devices specified for backup or restore; only 64 are allowed. RESTORE DATABASE is terminating abnormally. What can I do to restore the database? Must it be backed up with SQL server 2000 and then restored with SQL Server 2005? Please help!
Apparently you cannot go backwards. Once 2005 Express is installed, even removing it does not allow you to setup MSDE 2000 again. So there is no "trying it out" option.
Unfortunately, our software does not use 2005 Express. I tried it out, and now have a useless testing workstation that can't have MSDE 2000 installed again.
Any ideas on how to break the chain here are welcome.
Hello,I am hoping you can help me with the following problem; I need to process the following steps every couple of hours in order to keep our Sql 2000 database a small as possible (the transaction log is 5x bigger than the db).1.back-up the entire database2.truncate the log3.shrink the log4.back-up once again.As you may have determined, I am relatively new to managing a sql server database and while I have found multiple articles online about the topics I need to accomplish, I cannot find any actual examples that explain where I input the coded used to accomplish the above-mentioned steps. I do understand the theory behind the steps I just do not know how to accomplish them!If you know of a well-documented tutorial, please point me in the right direction.Regards.
I have a problem with trying to send a database from SQL Server 2005 to a server with SQL Server 2000. Now I KNOW that under normal circumstances, this isn't possible. But I tried to create a compatible SQL Server 2000 database using SQL Server 2005, sent it to the server, and tried to attach it, but it wouldn't attach. I even tried creating a database on the server end, send it to SQL Server 2005, modify it, and then send it back and it also wouldn't attach. I can't install SQL Server 2000 since Vista can't support it.
How can I configure a front end Access 2000 Database using Microsoft SQL 2000 as a back end environment? Could anybody help me by telling me what are the steps under SQL? Thanks everyone in advance.
Is it possible to uninstall SQL 2005 and reinstall SQL 2000 if I need to? I would obviously have a backup copy of the database(s) from the SQL 2000 version. If so, is this a major ordeal to perform?
We have installed SQL Server 2000 Service Pack 4 recently and have had various issues with some of our Stored Procedures. (which we didn't have with SP 3)
We are looking at our options regarding rolling back to Service Pack 3.
Can this be done ? & If so, is there a method documented on how to do this ?
I would appreciate a bit of advice here. There is a largish complaint here regarding a cutomer who has entered data in 1 of our online forms, but we suspect this was then overwritten by a cached form she also had open. Anyway to cut a long story short i need to roll back the database to a point in time.
Not something i have ever had to do.
The row where the id field is equal to 3352, and this would have been written to the database at 14:58:36 on 08-aug-2005. This was over written by the data in row with id 3380 at about 11am this morning, now is this is a live database on a webserver so i cant compromise its uptime as it get written to about 3 times a minute, so how should i go about this?
Hi All,Would someone give me an explanation on how SQL 2000 server backs up auser database? Is SQL server make a copy of user database first, andthen backup it up to a defined backup device? Or is it going straightto the defined backup device.Thanks,Bob.
I have a database being built that has a java front end, a SQL 2000 back end, and most of my clients are win98, will this work ok?? And if not do I need to upgrade to all w2k?
I am monitoring my replication process and I have a problem with the loop detection, I can see origined transacctions in the server, executed in the same for the replication.
The subscriptions configuration is sp_helpsubscription
We would like to install Sql 2005 Enterprise Edition (including database engine, reporting service, integration service and analysis service) as a sepearte instance on a server which already has Sql 2000 with reporting services and analysis services. We do not want to disturb the existing sql 2000 setup.
If we do that then what will happen to my earlier sql 2000 reporting service? Will it be upgraded to sql 2005 reporting service? I heard that reporting services are instance unaware application. Where will be the default reporting service database available?
i am a IT administrator ! I am now administer the webserver run SQL server 2005, running backup symantec exec . I want to know there is other better tool for sql backup ! I really dont like database much ! just want to know enough for administering them :mad:
After deleting all the test data from all tables in a SQL 2000 database, is there a way to reset all the auto-incrementing fields back to zero in one shot? In Access, you can run the Compact and Repair option. Also, in Sybase SQL, there was an "unload/reload" option to reduce the database size. Is there a similar function in SQL2000? Thanks for all the help
Hello,I'm trying to create a simple back up in the SQL Maintenance Plan that willmake a single back up copy of all database every night at 10 pm. I'd likethe previous nights file to be overwritten, so there will be only a singleback up file for each database (tape back up runs every night, so each daysback up will be saved on tape).Every night the maintenance plan makes a back up of all the databases to anew file with a datetime stamp, meaning the previous nights file stillexists. Even when I check "Remove files older than 22 hours" the previousnights file still exists. Is there any way to create a back up file withoutthe date time stamp so it overwrites the previous nights file?Thanks!Rick
I'm trying to learn some VB programming with the VB 2005 Express Absolute Beginner Series video tutorials (which I think is great) and have come across a problem that I can't solve.
When I follow the instructions in Lesson 9 (Databinding Data to User Interface Controls) my application will display the data from the database correctly and I can edit it (and as long as the debugger is running the data remains changed). However, the changes won't propagate back to the database. I don't get any error messages but after I edit the data, save (with the save button on the BindingNavigator toolbar), and end debugging the data in my database remains unchanged. When I use a MessageBox to show how many rows where edited/updated in the
I get the correct number back. I'm sure the problem is not due to coding errors since I've also tried running the accompanying Lesson 9 project file that can be downloaded from MSDN and the problem persists.
I'm using Windows XP SP2, SQL Server 2005 Express Edition and VB 2005 Express Edition. I've tried installing SQL Server 2005 Express with a number of different settings, including default settings, but it doesn't make any difference.
Would greatly appreciate any feedback on this as I'm keen to resolve this problem so I can get on with the next tutorial lesson.
We are trying desperately to get away from Access (ADP) and move on to something else. SQL Server 2005 is the engine and Access is the front end. We desperatley need another front end. We torn between FoxPro or going Web Bassed. Can whats a good application tool that will asssit me in making our Databases webbased??
I am new to MS Sql Server, I have installed Sql Server on a system and i created a database in it, now i wanted to uninstall it and install it on other system, but i dont like to lose my database, therefore i want to export my schema and import in other database. what are the steps that i follow, i have installed Sql Server Management Studio Express on it.
Goal: set security on running specific stored procedures based upon user login and databse access
I have some DBA's who want to retain full control of databses / stored procedures as they now have but I want to restrict or rollback some of the changes that were implemented when the sql 2005 was set up. The sql 2005 EE is in a clustered system and uses Mixed Mode Authentication.
An example of what I want to restrict: The DBA's want to be able to view and kill processes for the different databases that are installed under their instance. The problem is other customer databases are also under the same instance.
Is their a way I can combine or have the stored procedure sp_lock only show the processes for the databases they have access to based upon their login? My concern is they will kill a process and affect the other customers.
New to Database Mirroring and I have a question about the Principal database server. I have a Database Mirroring setup configured for High-safety with automatic fail over mode using a witness.
When a fail over occurs because of a lost of communication between the principal and mirror, the mirror server takes on theĀ roll of Principal. When communication is returned to the Principal server, at some point does the database that was the previous Principal database automatically go back to being the Principal server?
I need to run two reports each of A5 Size to run back to page and print on single A4 paper means in 1st half Sale bill will be printed and in second half Gate Pass Will Be Printed both report will be on same page and size and shape should be maintained. How to do it.
Im using the free version of ms sql 2005 studio express. I can upload databases, edit them and check them etc.
how do I back them up on to my pc, I do not have the server with me, my ms database is hosted on namesco.co.uk hosting.
I know how to right click the database, click task and back up. But I dont know where to back it up?
Whenever I try to back up to somewhere on my c: drive it won't. I think it also only backs up on a .bak files. Which I don't have.
I've looked on the net and it says you need a seperate hard drive or tape drive for back. Do I need to add another hard drive to my pc, if yes what do I format it as. And also how do I get a .bak file?
Here is a screenshot of where I can get to:(you might have to copy and paste them in your browser, there bmp so are big images)
http://www.uktattoostudios.co.uk/images/ms1.bmp
http://www.uktattoostudios.co.uk/images/ms3.bmp
As you can see I dont have a .bak to choose so it comes up this. If I click ok and try and back it up, it says back up complete. However when I go in the folder there is no .bak file
I also read on the net that if there shared databases the hosts are the only ones who can back stuff up, I asked them and they said that I should be able to do it on ms sql studio express.
We have a weird problem in our test SQL 2005 SP1 - Windows 2003 Enterprise SP1 - Server (after upgrading from SQL 2000).
While changing data via JBOSS - JDBC connection, we get all our data modifications rolled back.
Selects are fine. Same SQL 2005 Inserts/Updates through JBOSS are fine on other machines with Windows XP (JBOSS is on the same machine there, while in troubled configuration it's on its own server).
But in production imitation environment we can't modify data.
I am using MS SQL Server 2005 Express edition with my application.
I am new to SQL Server.. Can any body help me in solving the following:
1) Is there any automatic back-up provision available in MS SQL Express edition ? 2) How can i take the back-up/archive my data ? 3) How to implement Data aging & Data pruning by using MS SQL Express edition 2005 ?
I am trying to send a file from SQL 2005 back to our AS400 DB2 db. First time trying to get this to work in SSIS.
I have a couple fields that are datetime in SQL Server and see SQL server sees datetime fields from DB2 as string so I am converting them to Strings using derived columns. That part seems to work fine. Get no errors on that part.
The conversions seem like they are working but it is faling when it tries to send it to as/400. I get the following error: any ideas on what is wrong?
[OLE DB Destination [1569]] Error: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available. Source: "IBMDA400 File Rowset" Hresult: 0x80004005 Description: "CPF5029: Data mapping error on member DSSCNTL. ". An OLE DB record is available. Source: "IBMDA400 File Rowset" Hresult: 0x80004005 Description: "CPF5035: Data mapping error on member DSSCNTL. ". An OLE DB record is available. Source: "IBMDA400 File Rowset" Hresult: 0x80004005 Description: "CPF5035: Data mapping error on member DSSCNTL. ".
I even created a sql table with same field sizes as one I am sending to AS400 and its sucessful there. So seem like it mght have somthing to do with sending to AS400 but not sure what.
This is the following Error when i tried to back up database in MS SQL SERVER 2005 Express Edition.
" TITLE: Microsoft SQL Server Management Studio Express ------------------------------
Backup failed for Server 'OFIX07SQLEXPRESS'. (Microsoft.SqlServer.Express.Smo)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.2047.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Backup+Server&LinkId=20476
System.Data.SqlClient.SqlError: The backup of the file or filegroup "sysft_article" is not permitted because it is not online. BACKUP can be performed by using the FILEGROUP or FILE clauses to restrict the selection to include only online data. (Microsoft.SqlServer.Express.Smo)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.2047.00&LinkId=20476