I am in the process of migrating from Sql Server 2000 to 2005. Part of my plan is to move some database's to 2005, but use the 2000 compatibility mode for the short term. My issue is this, our DR boxes are still on SQL Server 2000, would I still be able to use our log shipping processes? Or would I be better off in starting with migrating the DR boxes to 2005 first?
Thanks in advance.
Hi All
I€™m having a problem setting up maintenance plans on one of our SQL 2005 servers but first here€™s a bit of back ground.
The server is a Virtual machine running win2k3R2 SP2 server std and SQL 2k5, A supplier arrived to install and app on the server when discovering there app didn€™t work with 2k5 they seem to have set the 2 dbs on the server into 2k compatibility mode and set the entire SQL install to think its a 2000 install. (I€™m not sure how this is done all I can see is the wrong version number in management studio) The problem this is giving me it that the folder in management studio for Database Maintenance Plans is no longer under the management folder instead it under a sub folder called Legacy (which is how management studio seems to deal with all registered 2000 instances) and as such a can no longer right click and create new database maintenance plans is there any way around this or will I have to setup my backup job manually?
Ohh and have the supplier shot at dawn
Thanks All
Jon
Can you run SQL Server 2005 in SQL Server 2000 compatibility mode and still use it with Reporting Services 2005?
View 4 Replies View RelatedCan someone tell me if I can use the Gui tools which come with SQL Server 2005 against 2000 databases ?
View 1 Replies View RelatedWe have an environment where 3 SQL 2000 servers exist; one production servers and two standby servers that receive logs via log shipping. Everything works fine and it is stable. My client wants to get a new 64 bit server and run SQL 2005 64 bit version for the production box. Can we still do log shipping with the two remaining SQL 2000 boxes or do they all have to be on the same version and bit version?
Thanks
Bill
I know my problem is not directly associated w/ SSIS, so please forgive the post here. I figured this would be the "most" appropriate place to post this challenge.
We're attempting to edit a 2000 DTS package in Design mode from within the 2005 SQL Management Studio. To do this we downloaded/installed the following packages from the MS download site:
Microsoft SQL Server 2000 DTS Designer Components
Microsoft SQL Server 2005 Backward Compatibility Components
We're able to open the package in design mode from the Management Studio (Server > Management > Legacy > Data Transformation Services > DTS Package Name). But, when the DTS designer is open, the backspace and arrow keys won't respond in the Management Studio. They begin responding when we close the DTS designer. There are no error messages when we close the DTS designer.
Does anyone know of a fix or a workaround? Any help would be greatly appreciated.
Thanks, Mike
Hi
I have a question about change of compability.
I want to change compability level from 2000 to 2005 on a very large database with a lot of indexes. I have heard that if I change compability level the indexes will no longer be usable.
Is it enough to just rebuild all indexed after I have changed compability level or do I have to do something else?
On my current contract we have a SQL 2005 box with a user database and the tempdb database in 6.5 compatibility mode. I would like to remove the user database and change the tempdbs compatibility mode. When you try and use EM just about everything fails with errors about collation or syntax. From what I have found it could be related to the tempdb being in 6.5 compatibility mode but either way I would like to remove this old unused DB.
My question is after I remove the user DB and reset the tempdb compatibility mode what will or could break? I haven't been able to find much on what would change or what to look out for after the change is made. Has anyone else done this? If so what issues did you face.
Thanks
Doug
Hi,
I have a database that is in the SQL Server 2000 compatability mode on my SQL 2005 server. I am trying to restore a backup of this database on my SQL Server 2000 database on another server and keep getting strange messages. First trying Red-Gate and then plain SQL Server with no luck.
It seems as I remember that the 7.0 and 2000 compatibility issue between backups did not arise when the compatibility mode was set to 7.0.
Is this "planned" behavior or an "undocumented feature"??? Anyone else have success doing this?
Thanks,
John Campbell
Hi,
We are planning to upgrage our SS 2000 databases(couple of hundreds) to SS 2005.
To minimise the potential work arounds, it is agreed to have complex databases, continue running on compatibility mode 80. What are the potential impact of having database on mode 80(apart from not being able to use new feature)on SS2005?
Fruther how we can we import SS 2000 DTSs to SS 2005 SSIS in an cluster environment?
Thanks,
Sajish
I have moved a database from SQL 2000 to SQL 2005 Express. I have modified the structure in 2005 Management Studio Express.
Now I cannot attach to the modified dataabse in SQL 2000 Enterprise Manager. I get "Error 602: Could not find row in sysindexes for database ID.... Run DBCC CHECKTABLE on sysindexes".
This occurs despite the fact that I have kept the database at Compatibiluty Level SQL Server 2000, as reported in 2005 Management Studio Express.
Are 2005 and 2000 databases not compatible?
Many thanks.
I find that the "Create Table" script generated by SQL Server 2005 is in format:
CREATE TABLE [dbo].[City](
[CityID] [int] IDENTITY(1,1) NOT NULL,
[Name] [nvarchar](50) COLLATE SQL_Latin1_General_CP1_CI_AS NULL,
CONSTRAINT [PK_City] PRIMARY KEY CLUSTERED
(
[CityID] ASC
)WITH (IGNORE_DUP_KEY = OFF) ON [PRIMARY]
) ON [PRIMARY]
Can this appliable in SQL Server 2000 or MSDE? If not, how should I change it to make it work in both SQL 2000 and 2005?
Thanks
I find that the "Create Table" script generated by SQL Server 2005 is in format:
CREATE TABLE [dbo].[City](
[CityID] [int] IDENTITY(1,1) NOT NULL,
[Name] [nvarchar](50) COLLATE SQL_Latin1_General_CP1_CI_AS NULL,
CONSTRAINT [PK_City] PRIMARY KEY CLUSTERED
(
[CityID] ASC
)WITH (IGNORE_DUP_KEY = OFF) ON [PRIMARY]
) ON [PRIMARY]
Can this appliable in SQL Server 2000 or MSDE? If not, how should I change it to make it work in both SQL 2000 and 2005?
Thanks
Is it possible to load a sql express database into a sql 2000 server?
Someone in another department installed sql express and has an application using it, but its database
will grow over 4 gb so I need to move the database somewhere. We currently only have sql server 2000 in production so I was wondering if I could use our 2000 server.
thanks
We are going to upgrade to windows 2000 in the near future.
We currently use sql server 6.5.
Can anyone tell me if SQL 6.5 will run on windows 2000?
Also will SQL server v7 run on windows 2000 or do I need to upgrade to SQL 2000?
Many thanks.
A client just purchased a new notebook, pre-installed with Vista. He says he is having trouble installing SQL Server 2000 (database and client tools). I am not certain (yet) if this is the standard edition or the desktop version.
What, if any, are known compatibility issues between SQL 2000 and Vista?
Hallo Everyone,
I have an SQL database that I need to detach from an SQL2005 server and reattach to an SQL 2000 database. I tried to set the Compatibility level from SQL Server 2005 (90) to SQL Server 2000 (80). This did not work
Any ideas?
Nigel...
I work for a small state government department. We are about to install SQL Server 2005.
A national government department that runs on SQL Server 2000 are willing to give us a backup of their database (20 gig I think) and then log ship to us regulary. Our aim is to have a copy of the database that we can query from and that is only a day or so out-of-date.
I'm having no luck.
1. I can backup the SQL Server 2000 database.
2. I can restore the SQL Server 2000 database onto the SQL Server 2005 box no worries.
2. BUT, if I attempt to restore the 2000 database with the option 'Leave the database in read-only mode ...' selected (so that I can then restore transaction logs and it's read-only), then I get an error message. ""This backup cannot be restored using WITH STANDBY because a database upgrade is needed. Reissue the RESTORE without WITH STANDBY.". I'm doing all this using SQL Server Management Studio.
It appears we will have to use SQL Server 2000 rather than 2005 to get this working.
Q: Has anyone successfully done this from SQL 2000 to SQL 2005 please? If so, how was it achieved please?
Thanks.
Hi
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?
Please help us.
Regards,
Sankar N
I am implementing log shipping in sql server 2000.The logs are been backed up on the source server but they are not been restored on the destination server.What could be the possible reason for this?
Thanks
Madhukar
------------
Robbie at 3/7/2002 10:13:00 AM
Great news but how??
------------
mmwops at 3/7/2002 9:09:32 AM
can be done
------------
Robbie at 3/7/2002 7:03:16 AM
Does anyone know if Log Shipping be done using SQL Server 2000 standard edition or does this have to be Enterprise??
Many Thanks
Robbie
I am currently running a Standard Edition of SQL 2000 on a WIndows NT4.0 Platform with service pack 6a installed. I want to implement Simple Log Shipping on my Standby Server as a means of improving my ability to recover from a contingency.
The Setup is as follows:
1. Both the SQL Server Service and SQLAGENT Service on the Primary Server Start with a Domain Admin Account
2. Both the Primary and Standby Server have mixed authentication
3. The current security context of the User (Which happens to be a Domain Admin) is used for the Link Server Relationship.
4. The Directory on the Standby Server where the Transaction Log gets backed up to has permissions of "Everyone" - Full Control" as does the log file itself.
The error I am receiving is as follows:
Executed as user: xxxinvbsg. Backing up Northwind to
DISK=S5ad$yyyNorthwind_20020130_1540_LOG.BAK [SQLSTATE 01000] (Message 0)Processed 1 pages for database 'Northwind', file 'Northwind_log' on file 1. [SQLSTATE 01000] (Message 4035) BACKUP LOG successfully processed 1 pages in 0.264 seconds (0.007 MB/sec). [SQLSTATE 01000] (Message 3014) Execute [s5a].master.dbo.sp_ApplyStandByLog 'Northwind',N'S5ad$yyyNorthwind_20020130_1540_LOG .BAK',N'd:yyyUNDO_Northwind.DAT'
[SQLSTATE 01000] (Message 0) Executing RESTORE LOG Northwind FROM
DISK='S5ad$yyyNorthwind_20020130_1540_LOG.BAK' WITH STANDBY='d:yyyUNDO_Northwind.DAT [SQLSTATE 01000] (Message 0) RESTORE LOG is terminating abnormally. [SQLSTATE 42000] (Error 3013) Cannot open backup device 'S5ad$yyyNorthwind_20020130_1540_LOG.BAK'. Device error or device off-line. See the SQL Server error log for more details. [SQLSTATE 42000]
(Error 3201). The step failed.
Any help on this will be appreciated.
Thanks
Brad
I'm attempting to configure log shipping on 2 servers with SQL Server 2000 sp4 Enterprise Edition. I keep getting the following error when the job attemtps to execute.
Error 14261: The specified primary_server_name.primary_database_name('C')
already exists.
I have tried this KB http://support.microsoft.com/kb/298743 and i got the same error again!
Please HELP!
Hi,
I am now trying to configure Log Shipping in my compeny but I have encountered some difficulties. The destination site and the source site are far from each other and the transaction logs are too big, this situation causes an huge overload on our private network (we use WAN which is complitly disconnected from the internet). Is there any way to compress the transacion logs with zip or rar and combine it in the log shipping mechanizem?
Is there another way for making this files smaller?
I would be greatful for any ideas in this matter.
Thanks in advance,
Zvi Gilinsky
Hi,In the MS SQL 2000 Server, if the log shipping is set up right, does thatmean data in primary server changed will mapped to secondary server lateron?Thanks.Jason
View 4 Replies View Related
Hi,
I have maintanance plan for log shipping.it was working fine for last 2 months.But due to some reason I have to restart the server and after that my log shipping job was failed.When I start the job it is showing error "Executed as user: OKS-MARAdministrator. Invalid drive specification 0 File(s) copied. Process Exit Code 4. The step failed".This error is coming when I copy the bakup database file to another server.I have checked all the mapping and sharing option.Also I have nt changed anything in the two servers.But still then the error is coming.
Can you please help me out to shot out the problem?
Thanks in advance.
Sunanda
hi,
i have log shipping between 2 servers on sql server 2000. the log shipping failed because of some problem with transaction log backup files. somehow the files are missing and it is not able to apply transaction log. can someone please tell me how can i restore the log shipping between 2 servers. please help asap..need to fix it in couple hours
I am attempting to move some SQL 2000 databases to SQL 2005. My main production database does not seem to want to move. When I use the SQL 2005 GUI the .bak backup file is marked 'Incomplete'. When I attempt to restore the backup file I get a 'RESTORE detected an error on page (0:0) in database' message. I saw a thread in the SQL Express forum suggesting trying to restore from the T-SQL level to get the GUI out of the picture and I get the same 'error on page (0:0)' message. However when I take the same file and use SQL 2000 Enterprise Manager it restores with no problems.
Any ideas?
Thanks
Mike Mattix
Hi, I am trying to edit some data from a SQL2000-datasource in ASP.NET 2.0 and have a problem with a column that has bit-data and is used for selection. SQL2005 works fine when declaring <SelectParameters> <asp:Parameter DefaultValue="TRUE" Name="APL" Type="boolean" /> </SelectParameters>When running this code with SQL2000, there are no error-msgs, but after editing a record the "APL"-column looses its value of 1 and is set to 0. Looks like an issue with type-conversion, we've hit incompatibilities between SQL200 and 2005 with bit/boolean several times before. So, how is this done correctly with SQL2000? (I've tried setting the Type to "int16" -> err. Also setting Defval="1" gave an err) ThanksMichael
View 2 Replies View RelatedHey all-
I am working to establish a backup plan for SQL Server 2000. We are currently doing log shipping between servers.
A full backup once a week
transaction log backup every hour
We run a bulk deletion (delete * from table where date < ninetydays) which deletes 22,000 rows approximately. We are running in Full Recovery mode.
I wonder if there was anyway to improve my backup plan, preferably minimizing logging when the deletion takes place but still backup the data with log shipping.
Let me know if any of you have ideas. Thanks
Nate
SQL 200 introduce changes to licensing. There are two licensing modes, Per Seat and Per Processor.
Is there a way to change the licensing mode from Per Seat to Per Processor for a current SQL Installation
Do you know of any resources in terms of Transact SQL in order to migrate from 6.5 to 2000?
View 1 Replies View RelatedHi,i have SQL 2000 and 2005 on same machine(with different intance names,of course), my laptop - XP with SP2. The 2005 works fine but i can'tconnect on SQL 2000. All the the SQL services are started.Any idea? Have i to reinstall 2000?Tks,Lourival
View 1 Replies View Related