| Author |
Topic |
|
law76
Starting Member
4 Posts |
 Posted - 2004-06-30 : 10:20:28
|
| Hi All, I have an installation of SQL server 2000 which has had SQL Service pack 3 applied to it. However one of the databases in the SQL server does not work with this particular service pack, does anyone know the best way to roll back the system. Please note that the people who updated to SP3 did not back up the msdb, master or model databases before the upgrade. I am wondering if I do a backup of the database in question is it possible to restore that database to an SQL server running service pack 2 (any compatability issues). What I had in mind was to either do a full back up and restore the db with the move command to another SQL box that is running SP2 however I do not know if it is this straght forward, I also thought of detaching the DB from the SQL server with SP3 and then attaching it to the SQL server with SP2. Does anyone know if this will cause an issueRegardsLeighton |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2004-06-30 : 13:09:52
|
| Detaching and attaching will be the easiest for you.http://support.microsoft.com/default.aspx?scid=kb;en-us;224071But what problems are you encountering with service pack 3. I haven't heard of anyone having to rollback from it. Have you applied the security patch for service pack 3? It includes some bug fixes.Tara |
 |
|
|
law76
Starting Member
4 Posts |
Posted - 2004-06-30 : 18:34:29
|
| Thanks for your reply Tara, It is actually the program that I am running that states that service pack 3 is not currently supported. Just to clarify do I have to move the msdb, model, and master databases. Is it possible to just move my database to the new server without these other databases?Regards |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2004-06-30 : 18:36:01
|
| You can just move your databases, but you will lose DTS packages, jobs, maintenance plans, logins, or anything else not contained in the user database. You won't be able to move the system dbs anyway since they are a different service pack level.Tara |
|
|
|
law76
Starting Member
4 Posts |
Posted - 2004-06-30 : 18:43:54
|
| Tara, just to clarifyThe database actually works it is one of the frontends that works with this database that is causing the issue. Basically there is a ASP page that accesses the data in this database however there is a particular hotfix that is rolled into service pack 3 that changes the security settings in sql server which inturn makes this ASP page error out when accessing the backend. I have taken a backup of the database in question and restored it to another sql server which is running SQL server service pack 2. This seemed to work correctly however I am not sure whether the msdb, master and model databases need to also be copied to this machine. regards |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2004-06-30 : 18:47:12
|
| You can't copy the system database to the other machine anyway since they are different service packs. Do you know which security setting was turned on? I know that cross database ownership chaining was turned off, but it can be turned back on afterwards. You actually can select to have it on during the installation.Tara |
|
|
|
eyechart
Master Smack Fu Yak Hacker
3575 Posts |
Posted - 2004-06-30 : 19:05:17
|
| I had security problems with a distributed query that needed to be rewritten after applying SP3. It really wasn't that big of a deal though, since that code needed a rewrite anyway.Is there any possibility of fixing the ASP code, rather than going back to SP2? Is it an in-house app, or a 3rd party app?-ec |
|
|
|
law76
Starting Member
4 Posts |
Posted - 2004-06-30 : 20:42:27
|
| Thanks Tara and ec, ec in regards to the ASP it is unfortaunatley 3rd Party so I cannot change it directlyRegards |
|
|
|
eyechart
Master Smack Fu Yak Hacker
3575 Posts |
Posted - 2004-07-01 : 02:03:07
|
quote:
Originally posted by law76
Thanks Tara and ec, ec in regards to the ASP it is unfortaunatley 3rd Party so I cannot change it directly
Can you isolate the code that is causing the problem and post the exact error you are getting? I wonder if it is related to the cross database ownership issue that Tara mentioned. That would be an easy thing to fix w/o having to go back to SP2.-ec |
|
|
|
|
SQL Server Rollback?