Performance Is Degraded Drastically After Migrating To SQL Express 2005 From MSDE 2000

Dec 29, 2006

Hi,

Recently we have migrated our application from MSDE 2000 to SQL Server Express 2005(SP 1). This has significantly reduced the performance of our Windows.NET application which is developed using C#.

For example : While logging in to the application two databases are being attached.

Time taken in MSDE: 16 secs

Time taken in SQL Server Express 2005 : 58 secs
Also note performance is degraded for normal screens where data is retrived from database using inline queries.

Questions:

1) Is there any special(optimum) configuration(installation parameters) while installing the SQL Server Express 2005 setup?



2) Is there any query optimization to be done w.r.t SQL Server Express 2005 ?



We highly appreciate any help towards resolving the above problem.
Regards,
Sasi

View 8 Replies


ADVERTISEMENT

Temporary Table Insert Performance Degraded After Migration To 2005 By 50%.

Apr 11, 2007

Hi,



I have a series of queries which have doubled in the amount of time they take to execute since moving to SQL Server 2005. The queries being performance tested are utilising hardware that is very similar to that of the comparison SQL Server 2000 server. They have 6 CPUs exactly the same and we have swapped RAM around to eliminate that difference.



There are 4 parts to the query suffering performance degredation.



1. Create temporary results table

2. Create (using SELECT INTO) and populate temporary working table 1 - 212,263 rows

3. Create (using SELECT INTO) and populate temporary working table 2 - 5,102 rows

4. Insert into temp results table matches found in temp work table 1 and temp work table 2 - 382 rows



On 2000, the queries take a total of 15 secs. On 2005, they take 30 seconds. Part four of the query takes approx 17 secs on its initial run. However, if i truncate the temp results table and re-run just the last query it only takes 1 sec. Query Plan caching?



I have reviewed the forum for a solution to the problem but with no luck. Many of the solutions presented appear to relate to permanant user tables. Solutions such as UPDATE STATISTICS and recompiling stored procedures have no positive effect. When reviewing the query plans, there are very little differences. Some expected between versions right?



The following code snippet is the query from part 4.




Code Snippet

INSERT #MatchingResults

(Table1IDNo, Table2IDNo, MatchRunNo)

SELECT DISTINCT #Table2.IDNo AS Table2IDNo,

#Table1.IDNo AS Table1IDNo,

1 AS MatchRunNo

FROM #Table1

INNER JOIN #Table2

ON ( #Table2.LastName = #Table1.LastName )

AND ( #Table2.AddressDetails = #Table1.AddressDetails )

AND ( #Table2.Country = #Table1.Country )

AND ( ( #Table2.FirstName = #Table1.FirstName) OR ( #Table1.FirstName = '' ) )

AND ( ( #Table2.Title = #Table1.Title ) OR ( #Table1.Title = '' ) )



The query plan shows a hash join on both servers. I have tried removing the distinct statement and forcing a Loop Join (query hint).



I have also run SQL Profiler. The only differences there appear to be with the "SELECT StatMan" statements.



On 2000, part of the query duration is 1719 and is as follows:


Code SnippetSELECT statman([AddressDetails],[LastName],[FirstName],[Title],[Country],@PSTATMAN)
FROM (SELECT TOP 100 PERCENT [AddressDetails],[LastName],[FirstName],[Title],[Country] FROM [dbo].[#TMCT04042007101009_________________________________________________________________________________________________000000000096] WITH(READUNCOMMITTED,SAMPLE 3.675520e+001 PERCENT) ORDER BY [AddressDetails],[LastName],[FirstName],[Title],[Country]) AS _MS_UPDSTATS_TBL OPTION (BYPASS OPTIMIZER_QUEUE, MAXDOP 1)



On 2005, part of the query duration is 5188 and is as follows:


Code Snippet

SELECT StatMan([SC0], [SB0000]) FROM (SELECT TOP 100 PERCENT [SC0], step_direction([SC0]) over (order by NULL) AS [SB0000] FROM (SELECT [AddressDetails] AS [SC0] FROM [dbo].[#TMCT04042007101009_________________________________________________________________________________________________00000000000E] WITH (READUNCOMMITTED,SAMPLE 7.946877e+001 PERCENT) ) AS _MS_UPDSTATS_TBL_HELPER ORDER BY [SC0], [SB0000] ) AS _MS_UPDSTATS_TBL OPTION (MAXDOP 1)



Its clear that the sampling rate is higher. I assume this could have something to do with it. Can this be modified?



Thank-you for your help in advance..



Cheers



Tim















View 9 Replies View Related

Performance When Migrating From 2000 To 2005

Feb 10, 2008

Hi guys
We are in the process of moving from SQL Server 2000 to 2005. In this process in general I have noticed that performance is better as a result of the move but in a couple of specific cases performance is about 10 time worse as a result of the move and i am wondering if anyone can tell me why.

1) Should I be noticing that calling functions from within a where clause are slower in 2005.

2) Has the and/or logic processing been changed between the different versions.

3) Why does this segment of code run really slow in 2005 but really fast in 2000 (note, i know that its not nice looking but it is pre-existing code from before we came on board and there are more examples of these so its a bit of a change to go through and fix it all up to what it should be but i need to know why before i can move on and as i said i know its not nice and one should expect it to be slow but i specially need to know why it would run fine in 2000 and not on 2005):

.....
AND (Deleted = 0)
AND (DATEDIFF(d, dbo.GetStartOfDate(ReviewedDate), dbo.GetStartOfDate(GETDATE())) = 3)
OR (ProgressPointId = 32)
AND (Deleted = 0)
AND (DATEDIFF(d, dbo.GetStartOfDate(ReviewedDate), dbo.GetStartOfDate(GETDATE())) = 3)
OR (ProgressPointId = 30)
AND (Deleted = 0)
AND (DATEDIFF(d, dbo.GetStartOfDate(ReviewedDate), dbo.GetStartOfDate(GETDATE())) = 3)
....

Thanks for your help.
Anthony

View 5 Replies View Related

MSDE Performance Verses SQL 2005 Express

Aug 24, 2006

I have been testing one of our Apps under SQL 2005 Express and I am seeing a big downgrade in performance compared to MSDE on the same hardware. Has anyone else experienced this?

Cheers

Aussie Coder

View 5 Replies View Related

Migrating SQL EXPRESS In SQL 2000 Or 2005 Server

Mar 26, 2007

whenever i modified the connection of my current database...I'll always got an error,when asking for "server name"..it says [DBNETLIB...etc]Named Pipes etc error..my current database was SQLEXPRESS and i want to change it as an SQL OLEDB,2000,2005.. but as i said il always got an error..sometimes it says "SQL server does not exit..ODBC" etc...when im entering the "server name"..so i could only used Access or SQLEXPRESS server database.. what should i do with the error?? thanks for helping again..   

View 6 Replies View Related

Problem: Performance Difference Between MSDE And SQL Express 2005

Feb 4, 2007

Hello, all, I started out thinking my problems were elsewhere but as Ihave worked through this I have isolated my problem, currently, as adifference between MSDE and SQL Express 2005 (I'll just call itExpress for simplicity).I have, to try to simplify things, put the exact same DB on twosystems, one running MSDE and one running Express. Both have 2 Ghzprocessors (one Intel, one AMD), both have a decent amount of RAM(Intel system has 1 GB, AMD system has 512 MB), and plenty of GB offree disk space. MSDE is running on the Intel system, Express isrunning on the AMD system. To keep things fair I use the exact sameDB's and query on both systems. The DB's were created on MSDE so Isp_detach_db'd them from MSDE and then sp_attach_db'd them to Express(this is how MS says to do a "side-by-side" upgrade, so it'sacceptable to do so). After fighting problems in performancedifferences in different situations I have narrowed the problem downto this:Executing a simple select statement with join clause on the databasesyields a difference in execution time that is quite great. Using theExpress Management program I can run the query against either system(MSDE or Express, the two systems are connected via crossover cable toeliminate any network problems/issues). When running the queryagainst the MSDE system (which is over the network) I consistently get<20 ms response times on the query. When running the query againstthe Express installation (which is in shared memory) I consistentlyget 700 ms or longer response times. Both times are for the TotalExecution Time.The query is simply this: select db1.* from db1.owner.tablename as db1inner join db2.owner.tablename as db2 on db1.pkey = db2.someid wheredb1.criteria = 3So, gimme all the columns from one table in one DB (local to theinstallation), matching the records in another DB (also local to theinstallation), where one field in the first db matches a field in thesecond db and where, in the first db, one column value = 3.The first table has a total record count of 630 records of which only12 match the where clause. The second table has a total record countof about 2,700 of which only 12 match up on the 12 out of 630.Even though the data is the same and I've done the detach and attach,and even done the sp_updatestats, the difference in execution time isremarkable, in a bad way.Checking the Execution Plan reveals that both queries have the samesteps, but, on the MSDE system the largest consumer in the process isthe Clustered Index Scan of the 630 record table (DB1 in my queryexample), using 85%. The next big consumer is a Clustered Index Seekagainst the other table (2,700 rows), using 15%.The Execution Plan against the Express system reveals basically theexact opposite: 27% going to the Clustered Index Scan of the 630record DB1, and 72% going to the Clustered Index Seek of the 2,700record DB2.I'm sorry to be stupid but I have this information but I don't knowwhat to do with it. The best that I can tell from this is that thisis the source of my problems. My problems are that on my currentsystems that my clients use the data is returned to them faster thanthey can click the mouse and that the new system (that is, when theychose (or are forced by attrition) to move to Vista and thus Express2005) the screen pop is like 1.5 seconds. This creates poor userexperience. Worse, one process I allow the users to do goes fromtaking 14-30 seconds to over 4 minutes (all on the same machine withthe same OS and version of my program, so it's not a machine or OS ormy app problem).Anyway, I hope someone can shed some light on this now that I've paredit down some.Thanks in advance.--HC

View 9 Replies View Related

Problem Migrating Application Database From SQL Server 2000 To Express Edition 2005

Jan 21, 2008

Hi there

I am new to SQL Server, but the current project that I am working on has the following requirement:-

1) Migrate the application (a servlet based web application on Apache Tomcat) from Solaris to Wintel
2) Migrate the supporting database from SQL Server 2000 to Sql Server 2005
3) Get IIS to communicate with Tomcat for serving servlet/jsp etc to the client

Though I successfully completed item 1 above, am stuck at item 2. Details are below

Actions taken for item 2

A. Installed MS 2005
B. Created new database in MS 2005 (logged in as user 'sa')
C. Generated SQL scripts (such as create table table_A etc) from existing MS 2000
D. Genearted SQL scripts (such as insert into table_A etc) from existing MS 2000
E. Created new schema in MS 2005
F. Ran scripts C & D in the new schema. All tables are records populated.
G. Obtained new JDBC driver and test run to see if connection is working fine, and it worked. Even ran an sql statment


Code Block[select count(*) from sa.table_A]

and got appropriate response.


H. When I made the application to talk to this new database (which is a copy of Production from step C, D above), it's behaving as though it cannot find the record.
I. When I further debugged, I realised that the web application is excuting queries without mentioning the schema. For eg.



Code Block[Select firstName, lastName from table_A]

Or rather it assumes that the user connecting to database is same as the schema name.


J. To further ascertain my point, I ran the query


Code Block[Select firstName, lastName from sa.table_A]

and it worked!



Now the real problem is that I cannot modify the existing code to append a schema name and this approach is rather not recommended best practise.


I tried to match the user name with the schema name, even made this schema as default to the user. But still not finding any luck.

I request all you experts out there to help me out with this problem.

Regards,

prad.nair

View 3 Replies View Related

MSDE 2000 Upgrade To SQL 2005 Express

Apr 3, 2007

Hi,



I have 2 MSDE 2000 Instances installed on Windows 2003 Server STd w/ SP1.



The application relating to the default instance is being upgraded and will require SQL 2005 Express.



What is the best approach? So the named instance of MSDE 2000 still functions correctly.



Upgrade default instance of MSDE to SQL 2005, or install SQL 2005 Express to own path and restore the DB accross? Then remove the Default Instance of MSDE 2000.



Both MSDE 2000 Instances are listed in Add/Remove Programs.



Thanks

View 1 Replies View Related

MSDE 2000 And SQL 2005 Express On The Same Machine

Jul 26, 2007

Hi I would like to ask If its possible to have installed MSDE 2000 and SQL 2005 Express on the same machine. My computer uses MSDE 2000 for one application and I would like to install SQL 2005 Express for my own application. I would like to ask it will be a problem before I install it.
thanks a lot
Martin Molnar

View 1 Replies View Related

Msde 2000 - Sql 2005 Express Upgrade Issue.

Feb 16, 2007

Hey, This is my first time posting here but here goes nothing...

Ok I upgraded an xp machine running to sql express 2005 by doing the inplace upgrade. The upgrade process went great, after the upgrade I could connect to the databases that had been upgraded using the management studio.

BUT.

When I try to connect to the databases using the third party software which had always worked in the past I get the error when trying to access from both the client and server machines.

[DBNETLIB][Connection open()).]SQL Server does not exist or access denied.

I then tried setting up SQL express 2005 on another xp station just to test how things worked if it wasn't an upgrade. I installed, attached the databases (which I copied to that local machine) and I was able to connect to them through the third party software from the server machine, but not client machines. The client machines gave me the same error as above.

Does anyone have any ideas, I have been talking to the third party support but haven't gotten any where yet... does anyone have any suggestions?

Thanks,

View 4 Replies View Related

Installing MSDE 2000 On Server With SQL 2005 Express

Jun 14, 2006

Can anybody help?
I have a Windows XP and 2003 server; we have installed SQL 2005 Express on it but have an application that installs MSDE 2000 to connect to an application. After the MSDE 2000 is installed we can no longer see the instance across the network. If we uninstall the SQL 2005 express version we can see the Instance in MSDE 2000.
Is there any compatibility issue with install MSDE 2000 after SQL 2005 has been installed.
Many Thanks in advance
David

View 1 Replies View Related

Run Simultaneously Msde 2000 Instance And One Of 2005 Express, Possible?

Dec 2, 2006

Hi,
I got on my developer computer one instance of msde 2000. I want to test sql server express 2005, can I install it without "scrap" my other instance of 2000?

Strange question maybee, but it's what I wanna do!

Thanks all!

View 3 Replies View Related

Problems Upgrading Msde 2000 To SQL Express 2005

Apr 4, 2007

I am having issues trying to do an in place upgrade of msde 2000 to sql express 2005. When I try to upgrade it bombs when it reaches "Running action to shutdown instance(Run As Normal User)" with the following error:
Service 'computername' could not be stopped. Verify that you have sufficient privileges to stop system services. The error code is (16386).
I've tried an upgrade on a clean test machine, and it goes through without any problems. I am logged into an account with local admin permissions. If any one has any ideas, they would be appreciated.

View 1 Replies View Related

MSDE 2000 Or SQL Server 2005 Express (Beta) For New Project?

Apr 15, 2005

Hello guys! I have to develop a new web based project. It's a web
portal for events. At the moment it's runnung on an Access database.
The new version should be running on a SQL server - the desicion is:
MSDE 2000 or SQL Server 2005 Express (Beta). What do you recommend? The
webpages are developed under .NET 1.1.

View 3 Replies View Related

Can I Use SQL 2005 Reporting Services With SQL 2000 Server, SQL Express Or MSDE?

Feb 19, 2008

Hi, I'm wondering if I can use SQL 2005 Reporting Services with SQL Server 2000, SQL Express or MSDE, or I need to install SQL Server 2005 in order to use Reporting Services 2005? Thank you in advance.

Regards,
Miguel

View 1 Replies View Related

Upgrade From MSDE 2000 Release A To SQL Server 2005 Express

Jun 28, 2006

I'm trying to upgrade the Default Instance of MSDE 2000 Release A which is installed with Mixed Mode and strong password to SQL Server 2005 Express in a Windows 2000 Server with SP4.  On the Upgrade Logon Information screen, if I select SQL Server Authentication Mode, it will give me this message:

SQL Server Setup Cannot Upgrade the specified instance by using SQL Server Credential.  You must use Windows Authentication credential for the upgrade.

Thanks for any help.

View 1 Replies View Related

Moving Back To MSDE 2000 After Removing SQLServer 2005 Express

Sep 18, 2007

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.

View 1 Replies View Related

OLEDB Destination Performance Decreasing Drastically Over Time For Large Input Files

Jul 4, 2006

Hi,

We are processing 60,00, 000 rows(2 GB file) available in a flat file and loading them in to a database tables using OLEDB Destination components. In the data pipeline of an SSIS package we have 1 flat file source reader, 7 look up components(full cache mode), 1 multicast component and 2 OLE DB destinations with fast load option.

We have observed that first 10,00, 000 rows are processed and loaded in to target tables in just 4 minutes time. The second set of 10,00, 000 rows are processed in 15 minutes time. After this for processing each 1,00,000 rows SSIS is taking approximately 8 - 10 minutes time. We are not able to identify the reasons for the unexpected behaviour of SSIS.

We thought that as the input file size is 2 GB SSIS is not able to manage and slowing down over time of execution. We did split the big input file in to 60 small 37 MB (approx) size files. Then we modified the package by adding For-Each loop task to process all the 60 small files and load them in to database server sequentially. Even in this approach also we have identified data loading has slowed down drastically after processing 13 files.

In order to verify is there any problem with reading source file or transformation, we have replaced OLEDB destinations component with Flat File destinations. With Flat file destination the time taken for processing rows is very constant. For every 8 minutes package is able to process 10,00,000 rows and write them in to the destination files. So, there is no problem with the with either Look up components or flat file source reader.

We are sure that target database server is in same state/condition from the starting to the end of package execution. The client box in which we are running the package is having 1 GB RAM. During package execution time the CPU usage is at 30 % and PF usage is 580 MB. SP1 is also installed on both Client and Server.

Does any one have clue what is causing slow down of data load over the time of package execution?

View 3 Replies View Related

Migrating MSDE Db To SQLEXPRESS 2005

Mar 28, 2007

I'm rewriting an old application that has a MSDE database as backend. I'm estimating if upgrade the old db to SQL2005 or SQL2005 Express edition, so I'm trying to migrate it to different istances running on different servers. In order to manage servers, I'm using MSQL Management Studio of the SQL2005 evaluation edition. As first step, I have detached the MSDE .mdf file, and attached it to SQL Express server.



QUESTION 1: Is this the right procedure to migrate the db on SQL Express?

QUESTION 2: All seems to work, but in MSQL Management Studio if I point on a stored procedure of the migrated db in SQL Express and right-click, in the context menu doesn't appear the item: 'Execute stored procedure...'. This item instead appears also if I connect to the old MSDE database, and it's very nice during testing....

QUESTION 3: How to grant access in SQL Express server to the old users of the migrated db?



Thanks in advance.



Mike

View 1 Replies View Related

Upgrade From 2000 MSDE To 2005 Express - Enable TCP/IP By Default &&amp; Current Version Of SQL Running?

Jan 23, 2007

i am working on upgrading the clients and server computers from 2000 MSDE to 2005 SQL Express Adv. Plan to upgrade using the template.ini.

i can find the version of sql server running on th server by @@version but how do i find the version of client connctivity components the computer has installed in order to ugrade?

1. somehow i need to know whether to upgrade a client computer CONNECTIVITY COMPONENTS from 2000 to 2005?

2. is there a way to enable tcp/ip in installation script of SQL Express?


THANKS

View 9 Replies View Related

Migrating From Sql2000 MSDE Database To Sql2005 Express - Attach Database Errors

Apr 23, 2006

I have a medical records system, SoapWare v4.90, that uses MSDE (SQL2000) databases. Due to the 2gb limitation, I am trying to migrate over to SQL 2005 (Standard or Express) which I have heard works fine. The SoapWare has a datamanager that allows me to log in to the MSDE instance, detach the SoapWare databases from msde (as well as do backups, etc) which I can confirm are detached.

Then I log back into a SQL2005 database instance using the datamanager and try to attach the database. This is what their pictured instructions demonstrate. However, I get the following error:


Database 'sw_charts' cannot be upgraded because it is read-only or has read-only files. Make the database or files writeable, and rerun recovery.


Of course, some of the entries will be read only, since doctors have to sign off the charts and are not allowed to subsequently change them.  But I should still be able to switch over to sql 2005?!?!?!?


Or... is there a way to attach the databases to SQLExpress manually?

Help pls?

View 1 Replies View Related

Migrating From SQL Express To SQL 2005

Jul 1, 2007

Hi,I move my website to our production server who use SQL 2005 instead of SQL Express.The website was, of course, developped with SQL Express.Where can i find the steps that i need to configure the SQL 2005 server for working with my SQL Express database.Thanks

View 4 Replies View Related

Migrating DB's From SQL 2000 To 2005

May 15, 2007

Hi all,

I'm in need of migrating DB's from a SQL 2000 server to a new SQL 2005 server. Has anyone had any success in this or does anyone know of a process which would be best for this situation?

Here's my setup...

SQL2000 SERVER....OS - Server 2000
MDF's/LDF's reside on D:MSSQLData
Backups reside on D:MSSQLBackup

SQL2005 SERVER....OS - Server 2003
MDF's/LDF's reside on E:MSSQLData
Backups reside on E:MSSQLBackup

Any information on how to get these DB from 2000 to 2005 will be greatly appreciated.

View 9 Replies View Related

About Migrating To 2005 From 2000.

Jun 12, 2007

Hi, since havenot done migration yet, my company is planning to migrate from sql 2000 to sql 2005 server. and i am in group for capacity planning. can anybody suggest me the steps i should be really taking in order to migrate to 2005, if anyone has done the it in real world with database up to 50g.
thanks
Derek

View 1 Replies View Related

Migrating To 2005 From 2000

Mar 26, 2008

Guys! Very very junior in this migration part. Hope the seniors can help out....PLEASE!!!!!! Don't get me wrong asking you guys to spoon feed me. I have read a lot of articles and even BOL and also not to forget read millions of books on this. But just wanted to make sure that I am in the right path and want to do this without any problem. That's why I have decided to ask the Gurus here who have done this in past.

I have this machine now:

Microsoft SQL Server 2000 - 8.00.2040 (Intel X86)
Microsoft Corporation Enterprise Edition on Windows NT 5.2 (Build 3790: )


Migrating to this machine:

Microsoft SQL Server 2005 - (X64)
Microsoft Corporation Enterprise Edition (64-bit) on Windows NT 5.2 (Build 3790: Service Pack 2)

I have these in the SQL Server 2000 box:
1. Databases, tables (of course)
2. Views
3. Securities(Logins, Roles, Password)
4. DTS packages
5. Jobs
6. Replications
7. Linked Servers
8. Stored Procedures

Every article is different. I was confused at a point of time. Please show me the right way guys!

View 8 Replies View Related

Migrating From 32 Bit (2000) To 64 Bit (2005)

Mar 27, 2008

Yesterday I started this topic and I came step by step higher and now I have finalized my steps to migrate.

Seniors and Gurus and who has done this before, please review and correct me where I am wrong and/or add some tips for me to have this one going on successfully! Thanking all of you guys in advance! Here is what I have:

Before Migrating:
1. Install Service Packs, Security Patches and Hot Fixes
2. Install DTS Designer Tool from Microsoft to prevent conflict and failure of migrating current DTS packages to SQL Server 2005
3. Backup EACH and EVERY Database and double check the .bak files whether it exist and backup was successful
4. Just before migrating, reboot the server to clarify that the SQL Server Services and SQL Server Agent is working
When you are ready to migrate:
5. Make sure there are no users trying to connect to the OLD AND the NEW SQL Server. Inform them well in advance about the downtime. Shutdown any applications or websites that might be accessing the SQL Server.
6. Stop the SQL Server, SQL Agent and MS Search Services on the NEW SQL Server
If downtime is not possible:
7. For ever changing OLTP database, by the time you restore the backup onto the new server, the old server would have received more changes. To avoid this problem, you need to resort to log shipping. Log shipping is nothing but an automated process of backup and restore. The following steps will explain the process of log shipping (Note that SQL Server 2000 Enterprise Edition provides inbuilt logs hipping. We don't need that for this purpose. We can simply create a job that backs up and restores the databases
8. Create a job on the old server, with two steps. The first steps backs up the transaction log of the OLTP database. The second step restores this transaction log backup file onto the new server, using WITH STANDBY or WITH NORECOVERY option of the RESTORE command. Schedule this job to run every 10 minutes or 15 minutes, depending on the volume of transactions your OLTP database receives
9. This job will take care of shipping all new transactions since the full database backup, to the database on the new server. Let this job run until you can afford some downtime on your production database (that is, mid-night, or early morning, or a planned maintenance window)
10. Now to be doubly sure, no new transactions are coming in, set the database in 'single user' or 'dbo use only' mode. Take one last transaction log backup of the production OLTP database, and restore it onto the database on new server. This time use the WITH RECOVERY option of the RESTORE command
11. Run UPDATE_STATISTIC on User Database to reorganize all indexes
Considerations:
12. Security - The security model changed along with object ownership, but users that own objects will be turned into schemas and all of the object and role permissions will come over. These you will want to look over afterwards, but they should be ok.
13. Unless you have hundreds of them, it is always better to re-create them after upgrading. You cannot detach an MSDB database on a 2000 server and attach it on a 2005 server and have it work. Fortunate in this, we can script out the jobs from SQL Server 2000 and run it on the new SQL Server 2005
14. Typically you will have to re-create your replication too. Again, the good news is that you can generate the scripts for replication on a 2000 server and execute them on a 2005 server and it will create the appropriate articles and publications
15. For DTS packages, it is always recommended to use the Package Migration wizard to do this so that less or no problems will be encountered. Consider about the jobs previously set.
16. Logins can be created by using sp_hexadecimal and sp_revlogin2005

View 6 Replies View Related

Migrating SQL 2000 To SQL 2005

Jun 21, 2007

Hi Friends,Is there any tool or assistant to upgrade SQL 2000 to SQL 2005.Thanks,Arunkumar

View 2 Replies View Related

Migrating A SQL 2000 DB To A SQL 2005 DB

Mar 29, 2007

I would like to find out what the steps are to migrate a 2000 database up to 2005?



View 4 Replies View Related

Migrating From 2000 To 2005

Aug 14, 2007

Hello guys, I have vry basic question. I'm migrating from 2000 to 2005. MY question is do we have to recode all packages or just migrating of old 2000 DTS is fine. If so, then I can see only small icon of DTS package in 2005, whihc is not showing the details of DTS. Kindly, explain me what do i really do, migrating old one or re-creating new in 2005. Thanks in Advance

View 1 Replies View Related

Need Help Migrating From MySQL 5.0 To MS SQL 2005 Express

Oct 18, 2007

hello,

so as you can see i want to migrate from My SQL 5.0 to MS SQL Express. Is there any free tool provided by microsoft or something else i could to use to migrate my databases. I need this cause old web page was developed on PHP and now it's redeveloped on ASP.NET and i have very strange issues with ASP.NET and MySQL Lots of incompatibility and performace degradation, so i would like to try out MS SQL i think it must be better.

please guys help me out.

View 1 Replies View Related

Migrating 2000 To 2005 On Same Server

Apr 2, 2008

Has anyone had experience of migrating from 2000 to 2005 on the same box , and maintaining the SERVERNAMEINSTANCE_NAME.
What are some effective ways of migrating and retaining the same servername/instance name ?

The issue revolves around minimising the use of extra boxes , as I would like to do the migration on the same server and keep the name the same .

Jack Vamvas
--------------------
Search IT jobs from multiple sources- http://www.ITjobfeed.com

View 3 Replies View Related

Migrating SQL 2000 Database To SQL 2005

May 23, 2007

Hi,
I have a database on a SQL Server 2000, and would like to migrate it to a new server machine that has SQL Server 2005. has anyone already tried this, and can you please provide the steps to follow.

Thank you.

View 7 Replies View Related

Migrating From Sql Server 2000 To 2005

Sep 28, 2007



Hi,

We are migrating from SQL Server 2000 to 2005. We currently use ADO.Net to make connection to sql server. I just want to know after migration to sql server 2005 do we have to make any changes in code in the way we make connection to use ADO.Net2 which is part of sql server 2005. ??


Thanks
Arvind

View 1 Replies View Related







Copyrights 2005-15 www.BigResource.com, All rights reserved