SQL Server 2000 To 2005 Upgrade (Database Users Logins)

Jul 6, 2007

Hi All,

I have just migrated couple of test databases

from SQL Server 2000 to 2005 (side by side).



I also migrated the server level logins using SSIS transfer logins task, available on SSIS 'Transfer logins', I selected all the databases that I have migrated so that I have all database users account in server logins (to avoid orphaned users); but I don't have all the database users in server logins, also the sys.sysusers doesn't have the database users, that I have moved to SQL 2005. Can anybody help?



Also do I need to back up the SQL Server 2000 database and restore it on SQL 2005? What impact this operation can have?



Thanks for your time..



Bidyut



View 5 Replies


ADVERTISEMENT

Permissions To See Server Logins/Create Database Users

Feb 2, 2007

Our company has 2 Database Roles (DBE and DBA). The DBE creates
database schema, performs SQL Server Administration, and manages server
security. The DBA writes data access, ETL, and manages database
security. In 2005, we're struggling with how to allow the DBA to see
all of the logins on the server in order to add them as users of their
database. What permissions does the DBA need to select from any of the
logins on the server to add them to their database?



Michelle

View 1 Replies View Related

Sql 2005 Users Vs Logins

Feb 8, 2007

What is the relationship between the users in a database and the logins on the server.

View 1 Replies View Related

Database Users And Logins

Mar 20, 2006

Hi

I can't figure out what the purpose of having seperate users is as I can't actually login to the database using one.

Here is my scenario.

I have a single login called LoginA and I have a database which I want to carve up using schema's. At the database level I need to create a user, associate a login with this user and can set a default schema and specifiy what schemas this USER can access. The login created can access multiple schemas.

So..

I created a database login called loginA.

I created a user for the database called UserA set it's login name to LoginA and

I then created 3 schemas called SchemaA, SchemaB and SchemaC and set their schema owner name to UserA.

I went back to UserA and set their default Schema to SchemaA

How can I login using the new user created as it has no password associated with it. If I login using LoginA then I have no default Schema set becuase the schema is associated with a USER not a LOGIN.

I can understand why you can only have one login account assicated with one user account for each database but I can;t understand why you can specify a user name if you can't use it to login.

Has anyone got any ideas?

Thanks

View 1 Replies View Related

SQL 2005 - SQLDMO - Adding Logins/ Users

Jul 21, 2006

I do not understand the sequence in which to add logins/users. A coupleof things to note. I can not use vbscript - it has to be done using thesqldmo objects (or in a sql script).The sequence I use now is:1- create login, set default db2- add login to sql server3- set db owner4- create user5- add user to master db6- add user to tempdb - blows up hereError 'Microsoft SQL-DMO: [SQL-DMO]This object is already in acollection.'I need the user in 3 dbs. Any help greatly appreciated. Thinking aboutit...I bet by adding it to the master db that it is automatically addedto tempdb so I will try to add it to the 2rd db and see if that works.Thanks!-Will

View 2 Replies View Related

Transfer Logins From SQL Server 2000 To 2005

May 13, 2008

Hi

How to transfer logins from 2000 to 2005?


Raj.

View 1 Replies View Related

Database Upgrade From Sql 2000 To 2005

Oct 10, 2007



i am upgrading sql server 2000 database to sql server 2005 database.
I am using backup and restore method to upgrade.

i have an issues transferring the logins..

what is the best why to upgrade?????any info is appreciated..

View 10 Replies View Related

SQL 2000 Database Upgrade To 2005

Dec 12, 2006



Dear All..

I have a few databases running a sql2000 and the time as come to move them onto sql2005. Which would be the best route to take.

If I can think back to older version it was just a simply job of doing a backup in it's current version then restore in the new version? and upgrade was taken while restoring.. I could be wrong but any help !!

Thanks

Martin.

View 5 Replies View Related

Have Transferred Database && Users From Sql 2000 To 2005 But How Do I Transfer Their Permissions ?

Aug 14, 2007

We are currently running sql 2000 and are moving our database onto sql 2005 running on a different box.

We have managed to move the entire database, with users however the users permissions on specific tables/views/stored procedures have not been transferred, does anyone know a way of transferring user permissions rather then doing them all by hand?

The system is a large (over 500 table/views/stored procedures) and a very active one and therefore downtime is not optional.

any suggestions would be appreciated

Regards

Chris V

View 2 Replies View Related

Spin Loop Attaching Database In 2000 =&&> 2005 Upgrade

Apr 21, 2008

I just upgraded a large SQL 2000 database server to SQL 2005, and I have 2 databases that won't attach to the 2005 Server. They are both very small, about 90MB in size, and when I attach them to 2005, the process alternates between running and spinloop status. It can sit forever, and will never complete. I restored backups before the upgrade to a SQL 2000 Server, and reran DBCC CheckDB on both, and got no consistency errors, Updated Stats and indexes, then detached and moved the data files to 2005, and same thing.

View 3 Replies View Related

SQL 2000 To SQL 2005 Upgrade Error - Database Down - Updated - Help Appreciated

Jan 3, 2007

SQL 2000 to SQL 2005 Upgrade Error - Database Down - Help Appreciated

I am upgrading a SQL 2000 standard database server to SQL 2005 standard on a windows 2003 server

I am logged in as domain admin and started the upgrade as 'sa'

The upgrade stops with the error:

Service MSSQLSERVICE can not be started. Verify you have sufficient privilages to start system services. The error code is (17185)

The error log shows:

2007-01-04 15:59:38.77 Server      Authentication mode is MIXED.

2007-01-04 15:59:38.79 Server      Microsoft SQL Server 2005 - 9.00.1399.06 (Intel X86)

 Oct 14 2005 00:33:37

 Copyright (c) 1988-2005 Microsoft Corporation

 Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 1)

 

2007-01-04 15:59:38.79 Server      (c) 2005 Microsoft Corporation.

2007-01-04 15:59:38.79 Server      All rights reserved.

2007-01-04 15:59:38.79 Server      Server process ID is 4188.

2007-01-04 15:59:38.79 Server      Logging SQL Server messages in file 'F:SQLDataMSSQLlogERRORLOG'.

2007-01-04 15:59:38.79 Server      This instance of SQL Server last reported using a process ID of 2980 at 1/4/2007 3:56:58 PM (local) 1/4/2007 2:56:58 AM (UTC). This is an informational message only; no user action is required.

2007-01-04 15:59:38.79 Server      Registry startup parameters:

2007-01-04 15:59:38.79 Server        -d F:SQLDataMSSQLdatamaster.mdf

2007-01-04 15:59:38.79 Server        -e F:SQLDataMSSQLlogERRORLOG

2007-01-04 15:59:38.79 Server        -l F:SQLDataMSSQLdatamastlog.ldf

2007-01-04 15:59:38.79 Server      Command Line Startup Parameters:

2007-01-04 15:59:38.79 Server        -s MSSQLSERVER

2007-01-04 15:59:38.79 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.

2007-01-04 15:59:38.79 Server      Detected 4 CPUs. This is an informational message; no user action is required.

2007-01-04 15:59:38.83 Server      Set AWE Enabled to 1 in the configuration parameters to allow use of more memory.

2007-01-04 15:59:39.02 Server      Using the static lock allocation specified in the locks configuration option.  Allocated 20000 Lock blocks and 20000 Lock Owner blocks per node.  This is an informational message only. No user action is required.

2007-01-04 15:59:39.02 Server      Multinode configuration: node 0: CPU mask: 0x0000000a Active CPU mask: 0x0000000a. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.

2007-01-04 15:59:39.04 Server      Multinode configuration: node 1: CPU mask: 0x00000005 Active CPU mask: 0x00000005. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.

2007-01-04 15:59:39.04 Server      Attempting to initialize Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.

2007-01-04 15:59:41.04 Server      Attempting to recover in-doubt distributed transactions involving Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.

2007-01-04 15:59:41.04 Server      Database Mirroring Transport is disabled in the endpoint configuration.

2007-01-04 15:59:41.04 spid7s      Starting up database 'master'.

2007-01-04 15:59:41.05 spid7s      1 transactions rolled forward in database 'master' (1). This is an informational message only. No user action is required.

2007-01-04 15:59:41.07 spid7s      0 transactions rolled back in database 'master' (1). This is an informational message only. No user action is required.

2007-01-04 15:59:41.07 spid7s      Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.

2007-01-04 15:59:41.08 spid7s      SQL Trace ID 1 was started by login "sa".

2007-01-04 15:59:41.08 spid7s      Starting up database 'mssqlsystemresource'.

2007-01-04 15:59:41.11 spid7s      Using 'dbghelp.dll' version '4.0.5'

2007-01-04 15:59:41.11 spid7s      ***Stack Dump being sent to F:SQLDataMSSQLLOGSQLDump0035.txt

2007-01-04 15:59:41.11 spid7s      SqlDumpExceptionHandler: Process 7 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.

2007-01-04 15:59:41.11 spid7s      * *******************************************************************************

2007-01-04 15:59:41.11 spid7s      *

2007-01-04 15:59:41.11 spid7s      * BEGIN STACK DUMP:

2007-01-04 15:59:41.11 spid7s      *   01/04/07 15:59:41 spid 7

2007-01-04 15:59:41.11 spid7s      *

2007-01-04 15:59:41.11 spid7s      *

2007-01-04 15:59:41.11 spid7s      *   Exception Address = 78144D3A Module(MSVCR80+00014D3A)

2007-01-04 15:59:41.11 spid7s      *   Exception Code    = c0000005 EXCEPTION_ACCESS_VIOLATION

2007-01-04 15:59:41.11 spid7s      *   Access Violation occurred reading address 0000001E

2007-01-04 15:59:41.11 spid7s      * 

2007-01-04 15:59:41.11 spid7s      *

2007-01-04 15:59:41.11 spid7s      *  MODULE                          BASE      END       SIZE

2007-01-04 15:59:41.11 spid7s      * sqlservr                       01000000  02BA7FFF  01ba8000

2007-01-04 15:59:41.11 spid7s      * ntdll                          7C800000  7C8BFFFF  000c0000

2007-01-04 15:59:41.11 spid7s      * kernel32                       77E40000  77F41FFF  00102000

2007-01-04 15:59:41.11 spid7s      * MSVCR80                        78130000  781CAFFF  0009b000

2007-01-04 15:59:41.11 spid7s      * msvcrt                         77BA0000  77BF9FFF  0005a000

2007-01-04 15:59:41.11 spid7s      * MSVCP80                        7C420000  7C4A6FFF  00087000

2007-01-04 15:59:41.11 spid7s      * ADVAPI32                       77F50000  77FEBFFF  0009c000

2007-01-04 15:59:41.11 spid7s      * RPCRT4                         77C50000  77CEEFFF  0009f000

2007-01-04 15:59:41.11 spid7s      * USER32                         77380000  77411FFF  00092000

2007-01-04 15:59:41.11 spid7s      * GDI32                          77C00000  77C47FFF  00048000

2007-01-04 15:59:41.11 spid7s      * CRYPT32                        761B0000  76242FFF  00093000

2007-01-04 15:59:41.11 spid7s      * MSASN1                         76190000  761A1FFF  00012000

2007-01-04 15:59:41.11 spid7s      * Secur32                        76F50000  76F62FFF  00013000

2007-01-04 15:59:41.11 spid7s      * MSWSOCK                        71B20000  71B60FFF  00041000

2007-01-04 15:59:41.11 spid7s      * WS2_32                         71C00000  71C16FFF  00017000

2007-01-04 15:59:41.11 spid7s      * WS2HELP                        71BF0000  71BF7FFF  00008000

2007-01-04 15:59:41.11 spid7s      * USERENV                        76920000  769E3FFF  000c4000

2007-01-04 15:59:41.11 spid7s      * opends60                       333E0000  333E6FFF  00007000

2007-01-04 15:59:41.11 spid7s      * NETAPI32                       71C40000  71C97FFF  00058000

2007-01-04 15:59:41.11 spid7s      * SHELL32                        7C8D0000  7D0D2FFF  00803000

2007-01-04 15:59:41.11 spid7s      * SHLWAPI                        77DA0000  77DF1FFF  00052000

2007-01-04 15:59:41.11 spid7s      * comctl32                       77420000  77522FFF  00103000

2007-01-04 15:59:41.11 spid7s      * psapi                          76B70000  76B7AFFF  0000b000

2007-01-04 15:59:41.11 spid7s      * instapi                        48060000  48069FFF  0000a000

2007-01-04 15:59:41.11 spid7s      * sqlevn70                       4F610000  4F7A0FFF  00191000

2007-01-04 15:59:41.11 spid7s      * SQLOS                          344D0000  344D4FFF  00005000

2007-01-04 15:59:41.11 spid7s      * rsaenh                         68000000  6802EFFF  0002f000

2007-01-04 15:59:41.11 spid7s      * AUTHZ                          76C40000  76C53FFF  00014000

2007-01-04 15:59:41.11 spid7s      * MSCOREE                        61FB0000  61FF4FFF  00045000

2007-01-04 15:59:41.11 spid7s      * ole32                          77670000  777A3FFF  00134000

2007-01-04 15:59:41.11 spid7s      * msv1_0                         76C90000  76CB6FFF  00027000

2007-01-04 15:59:41.11 spid7s      * iphlpapi                       76CF0000  76D09FFF  0001a000

2007-01-04 15:59:41.11 spid7s      * kerberos                       62220000  62277FFF  00058000

2007-01-04 15:59:41.11 spid7s      * cryptdll                       766E0000  766EBFFF  0000c000

2007-01-04 15:59:41.11 spid7s      * schannel                       76750000  76776FFF  00027000

2007-01-04 15:59:41.11 spid7s      * COMRES                         77010000  770D5FFF  000c6000

2007-01-04 15:59:41.11 spid7s      * XOLEHLP                        622E0000  622E5FFF  00006000

2007-01-04 15:59:41.11 spid7s      * MSDTCPRX                       622F0000  62367FFF  00078000

2007-01-04 15:59:41.11 spid7s      * msvcp60                        780C0000  78120FFF  00061000

2007-01-04 15:59:41.11 spid7s      * MTXCLU                         62370000  62388FFF  00019000

2007-01-04 15:59:41.11 spid7s      * VERSION                        77B90000  77B97FFF  00008000

2007-01-04 15:59:41.11 spid7s      * WSOCK32                        71BB0000  71BB8FFF  00009000

2007-01-04 15:59:41.11 spid7s      * OLEAUT32                       77D00000  77D8BFFF  0008c000

2007-01-04 15:59:41.11 spid7s      * CLUSAPI                        62390000  623A1FFF  00012000

2007-01-04 15:59:41.11 spid7s      * RESUTILS                       623B0000  623C2FFF  00013000

2007-01-04 15:59:41.11 spid7s      * DNSAPI                         76ED0000  76EF8FFF  00029000

2007-01-04 15:59:41.11 spid7s      * winrnr                         76F70000  76F76FFF  00007000

2007-01-04 15:59:41.11 spid7s      * WLDAP32                        76F10000  76F3DFFF  0002e000

2007-01-04 15:59:41.11 spid7s      * rasadhlp                       76F80000  76F84FFF  00005000

2007-01-04 15:59:41.11 spid7s      * security                       62800000  62803FFF  00004000

2007-01-04 15:59:41.11 spid7s      * dbghelp                        671B0000  672C7FFF  00118000

2007-01-04 15:59:41.11 spid7s      *

2007-01-04 15:59:41.11 spid7s      *        Edi: 62FA0040:  62FA0028  671AFFF0  00000000  00000000  00000000  00000000 

2007-01-04 15:59:41.11 spid7s      *        Esi: 0000001E: 

2007-01-04 15:59:41.11 spid7s      *        Eax: 0416C05E:  C0400096  C0400416  00000416  000062FA  00000000  00000000 

2007-01-04 15:59:41.11 spid7s      *        Ebx: 0416C040:  0105F270  00002000  00000005  00000000  3368C1E0  00000000 

2007-01-04 15:59:41.11 spid7s      *        Ecx: 0105B010:  458B0046  01F88348  00D3850F  458B0000  89C23B50  0F342444 

2007-01-04 15:59:41.11 spid7s      *        Edx: 00000000: 

2007-01-04 15:59:41.11 spid7s      *        Eip: 78144D3A:  24FFA5F3  144E5495  C78B9078  000003BA  04E98300  E0830C72 

2007-01-04 15:59:41.11 spid7s      *        Ebp: 33D6E770:  33D6E790  01C65B97  62FA0040  0000001E  0416C040  0416C6DC 

2007-01-04 15:59:41.11 spid7s      *      SegCs: 0000001B: 

2007-01-04 15:59:41.11 spid7s      *     EFlags: 00010212:  0020006D  00690046  0065006C  005C0073  006F0043  006D006D 

2007-01-04 15:59:41.11 spid7s      *        Esp: 33D6E768:  62FA0040  33D6E7A4  33D6E790  01C65B97  62FA0040  0000001E 

2007-01-04 15:59:41.11 spid7s      *      SegSs: 00000023: 

2007-01-04 15:59:41.11 spid7s      * *******************************************************************************

2007-01-04 15:59:41.11 spid7s      * -------------------------------------------------------------------------------

2007-01-04 15:59:41.11 spid7s      * Short Stack Dump

2007-01-04 15:59:41.13 spid7s      78144D3A Module(MSVCR80+00014D3A)

2007-01-04 15:59:41.13 spid7s      01C65B97 Module(sqlservr+00C65B97)

2007-01-04 15:59:41.13 spid7s      01CA43B5 Module(sqlservr+00CA43B5)

2007-01-04 15:59:41.13 spid7s      01CA452E Module(sqlservr+00CA452E)

2007-01-04 15:59:41.13 spid7s      0217D3BD Module(sqlservr+0117D3BD)

2007-01-04 15:59:41.13 spid7s      0217B896 Module(sqlservr+0117B896)

2007-01-04 15:59:41.13 spid7s      0100889F Module(sqlservr+0000889F)

2007-01-04 15:59:41.13 spid7s      010089C5 Module(sqlservr+000089C5)

2007-01-04 15:59:41.13 spid7s      010086E7 Module(sqlservr+000086E7)

2007-01-04 15:59:41.13 spid7s      010D764A Module(sqlservr+000D764A)

2007-01-04 15:59:41.13 spid7s      010D7B71 Module(sqlservr+000D7B71)

2007-01-04 15:59:41.13 spid7s      010D746E Module(sqlservr+000D746E)

2007-01-04 15:59:41.13 spid7s      010D83F0 Module(sqlservr+000D83F0)

2007-01-04 15:59:41.13 spid7s      781329AA Module(MSVCR80+000029AA)

2007-01-04 15:59:41.13 spid7s      78132A36 Module(MSVCR80+00002A36)

2007-01-04 15:59:41.13 spid7s      Stack Signature for the dump is 0x2BEDE9E0

2007-01-04 15:59:41.27 spid7s      External dump process return code 0x20000001.

External dump process returned no errors.


2007-01-04 15:59:41.27 spid7s      Error: 17185, Severity: 16, State: 1.

2007-01-04 15:59:41.27 spid7s      Unable to update password policy.

2007-01-04 15:59:41.27 spid7s      SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.

Any clues?

Cheers

Paul

View 3 Replies View Related

How To Use Transfer SQL Object To Copy An Entire Database Including Logins And Users

Dec 14, 2007



I have read the previous threads on the bugs with this task mainly: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1438968&SiteID=1 . These are great posts that helpmed me avoid wasting time. I haven't seen one yet that addresses copying an entire database including the sql server logins.


I would like to import the ENTIRE database from one (2005) server to another(2005) using the SSIS Transfer SQL Object task (not just sprocs,tables,views and functions). I have figured out how to pull the tables,views,sprocs and functions ... by using an execute sql task to drop these objects. But I cannot get this to work for users since the user dbo cannot be dropped and guest can only be disabled. I am creating a new database (this is the database where the sql objects will be copied to) via management studio to test this. There has to ba a way to get this working ... Microsoft must have published some sort of KB article on this task or a Script Task using SMO object calls. If need be I can drop the entire database on the target machine and have SSIS recreate it.

The only reason I'm willing to take a risk with SSIS rather than backup and restore is because of time constraints (I assume the SSIS task is faster) and backup storage administration.


declare @name varchar(200)
declare @object varchar(200)
DECLARE object_cursor CURSOR READ_ONLY FORWARD_ONLY FOR
select table_name,table_type from INFORMATION_SCHEMA.TABLES
union
Select name,'SPROC' table_type from sys.procedures Where [type] = 'P' and is_ms_shipped = 0 and [name] not like 'sp[_]%diagram%'
union
select name,'FN' from sys.objects where type_desc like '%FUNCTION'
OPEN object_cursor
FETCH NEXT FROM object_cursor INTO @name,@object
IF @@FETCH_STATUS <> 0
PRINT ' <<None>>'
WHILE @@FETCH_STATUS = 0
BEGIN
if @object = 'BASE TABLE'
begin
exec ('drop table ' + @name)
end
else if @object = 'VIEW'
begin
exec ('drop view ' + @name)
end
else if @object = 'SPROC'
begin
exec ('drop procedure ' + @name)
end
else if @object = 'FN'
begin
exec ('drop function ' + @name)
end
FETCH NEXT FROM object_cursor INTO @name,@object
END
CLOSE object_cursor
DEALLOCATE object_cursor

View 4 Replies View Related

How To Upgrade SQL Server 2000 Cluster To SQL Server 2005 Cluster(Database)

May 8, 2007

Hi



We are planning to upgrade the SQL Server in our production environment from SQL Server 2000 to SQL Server 2005. This is a 4 Node cluster environment with 3 Databases on 3 Virtual instances. The main requirement is to achieve this with no/minimal downtime.



Could you please suggest or direct me to any documentation for the best practices used to upgrade such an environment?



Thanks

Priyanka

View 2 Replies View Related

Move Logins From A Sql 2000 Server To A Sql 2005 Server

Dec 4, 2006

Hi guys,
I have tried to use the sp_help_revlogin script to move logins from a sql 2000 server to a sql 2005 server. It works for users that have a password. But if the password is blank it will fail. Is there a work around for this since I can't change the users passwords?
I have also tried SSIS package but that too doesn't work because of the same reason.

Can anyone help...

View 1 Replies View Related

Sql Server Upgrade From 2000 To 2005

Jan 31, 2006

I am currently using sql server 2000 and I have just installed sql server 2005 in a separate box that will be used as the production server so I will be upgrading to the new database server soon.

I was reading the upgrade options for this situation and one option is to detach the 2000 database, copy the mdf and log files to the new server and attach it to mssql 2005. Another option is to recreate the tables, views, etc. and export/import the data to the new server.

I would like to ask what the best option is for this situation because I am not sure what the advantages and disadvantages of just detaching/attaching and recreating the database in sql server 2005. If I just detach/attach the database, will there be any disadvantage in the performance because the database files were created in 2000 and is functioning because of backward compatibility in 2005? Would it be better to recreate the database in 2005 and import the data from 2000 so that the database would be running in a way that is designed for 2005?

I am not really sure of the differences of these upgrade options so any ideas would be greatly appreciated.

Thanks in Advance

-Voltaire

View 7 Replies View Related

SQL Server 2008 :: Logins Or Users Without Any Permission?

Feb 13, 2015

How to find the list of logins/users who do not have any permission (except default Public) access.

View 4 Replies View Related

Getting All Logins / Users With Their Password Into Other Server While Doing Migration?

Jun 24, 2015

How to get all logins & users with their password into other server while doing migration?

View 7 Replies View Related

What Is Maximum No. Of Concurrent Logins Possible On A SQL Server 2005 Database?

Dec 19, 2006

what is maximum no. of concurrent Logins Possible on a SQL server 2005 Database?

View 3 Replies View Related

SQL Server 2005 Installation Or Upgrade From 2000

Jul 19, 2006

Hello, I have sql server 2000 personal edition on my PC and I have just got a 2005 DVD. I tried to install it but it is not working. I don't know how to manage my databases. As if there is no graphical managemnt tool. The 2005 is also Personal edition.
I reinstalled the sql 2000, and now I'm trying t upgrade to sql 2005, but still don't know how to do that.
Please someone help me!!!!!!!!!!

View 1 Replies View Related

Why Upgrade To MS SQL Server (be It 2000 Or 2005) From Access (say, 97)?

Dec 1, 2005

Probably this question has been asked hundreds of times and yet netsearch has not generated satisfactory enough answer, at least, to me.And OK, let's assume your organization has more than 200 employees,just one measure to indicate that it's not small and data processingneeds are quite extensive (for both OLTP and OLAP).We've heard so much about concurrency support, stability andperformance. Are there any real persuasive paper out there to talkabout it? Now, let me also put it in another perspective, say, you'rea Microsoft sql server sales guy or gal for that matter for newaccounts. What you got?Thanks.

View 5 Replies View Related

Sql Server 2000 Upgrade To 2005 Blocked

Mar 4, 2008

I've inherited 6 sql server 2000 boxes. I've upgrade 3 with no trouble. now I have one that gives the message :
"your upgrade is blocked because of cross-language compatibility rules.
For more information about cross-language support, see the version..."

all servers are 2003, sp2. All SQL is Enterprise edition, default language is "english". even the collation order is
the same. why the cross language message? Any help would be good else I'll be forced to rebuild the DB and load application again. ugly!!




dave

View 3 Replies View Related

SQL 2005 Express Upgrade To SQL 2000 Server

Aug 20, 2007

Hi all,

My question might be a little bit unusual, but is it possible to upgrade SQL 2005 Express (the free version of SQL) to SQL 2000 Server without any loss of functionality?

Where do I have to pay attention to when doing this?

Thanks in advance!

MMQ

View 1 Replies View Related

SQL Server 2000 To 2005 Replication Upgrade

Apr 17, 2008

Hi All,

Currently we use SQL 2K SP4 and snapshot replication with a Central Publisher with Remote Distributor toplogy.

I am looking to upgrade or migrate our SQL servers to SQL 2005 and was wondering what is the best way to do this for our replicated architecture?

Is the best way to run the SQL 2005 Upgrade on all 3 servers (publisher, distributor, subscriber) and should it automatically upgrade the servers including the replication components? Is there anything i should consider/watch out for when doing the upgrade and it involves replication (namely snapshot replication)?

Thanks in advance.

View 1 Replies View Related

Clustered SQL Server 2000 To 2005 Upgrade

Jun 12, 2007

I would like to upgrade a production active/passive SQL Server 2000 cluster to SQL Server 2005.

I've read all of the documentation I could find, and doing an in-place upgrade seems to be the way to go. (Despite the fact it scares the hell out of me.

But throughout all the documentation, I've yet to see some simple and fairly important questions answered.

How does the process of upgrading SQL Server work when you're dealing with a cluster?

Do you upgrade one machine then the other? If so, do you upgrade the active node first, or the passive node?

What happens if you're forced to failover from one instance to the other before you've had a chance to upgrade both to 2005? In other words, you failover from 2005 to 2000. Would that even work?

What happens if your upgrades fails for some reason? Is it easy to rollback the installation? If not, will reinstalling SQL Server 2000 cause any issues? Will it remember the previous configuration and simply fix the broken install?

Any help/insight would be greatly appreciated.

View 8 Replies View Related

SQL Server 7.0 Database Upgrade To 2000

Feb 9, 2001

I would like to upgrade my database from 7 to 2000, are there any white papers or guide i can read. Or dose anyone have advise they can give?

Thanks

View 1 Replies View Related

SQL Server Upgrade 2000 - 2005 Files Read Only But Not Really

Feb 28, 2006

Hi,

I'm trying to upgrade from SQL Server 2000 to 2005. The problem I am having is that when I try to attach the existing db files I get a message that says "database cannot be upgraded because it is read only or has read only files...."

Thing is... there is no write protection on the files.

Can anyone advise me on how to overcome this problem so that I can attach the db, please?



Thank you

Robert

View 25 Replies View Related

Server Level Role That Can Add / Alter Logins And Corresponding Users On All Databases

Jul 7, 2015

Does securityadmin Server level role can add, alter logins and corresponding users on all databases ? 

If not what is the best role other thn SA to have to manager logins and users.

View 4 Replies View Related

Upgrade An Active Passive Sql Server 2000 Cluster To 2005

Aug 14, 2006

I have upgraded our test server and on non cluster production machine. My next server is a cluster and I don't have a test cluster server. Do I upgrade the active node and that is all or am I going to need to fail it over and upgrade the other node.

Also the prerequesite for the upgrade advisor is .net 2.0 I am going to up that on each server one at a time but I am only going to add the upgrade advisor to one node is that ok.

I read the SP1 documentation and it clearly states only patch the active node and do not patch the inactive nodes.

View 1 Replies View Related

Apparent Successful Upgrade To 2005 But Old (2000) SQL Server Remains

Mar 15, 2007

I used the SQL Server 2005 Upgrade Advisor to upgrade from SQL Server 2000 Enterprise to 2005 Standard. The only complaint I got concerned DTS packages, but I had none anyway. When I open SQL Server Management Studio, I can run queries, but they're against tables in the old 2000 databases. The SQL engine and Server agent are version version 8.0. Not surprising that new TSQL statements like 'BACKUP SERVICE MASTER KEY TO FILE' won't work.

Do I have to uninstall my previous version before upgrading?

Thanks.

View 3 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

Logins From 2000 To 2005

Jun 22, 2007

As from what i see there are different system files for logins.



Is there a way to transfer SQL 2000 logins to SQL 2005 i am used to the

sp_help_revlogin i think thats the script..in 2000



Is there a way to convert all logins from SQL 2000 to SQL 2005

View 3 Replies View Related

Can MSDE 2000 Upgrade To SQL Server 2005 Standard Edition Directly?

Jul 3, 2006

According to this http://msdn2.microsoft.com/en-us/library/ms143393(d=robot).aspx, it seems that it cannot. But is this a complete chart?


Thanks for any help,

Peter

View 5 Replies View Related

SQL Server 2000 Vs Sql Server 2005 Upgrade Problem Any Ideas?

May 14, 2007



In our application we use the ADODB.Recordset.



In SQL server 2000



If there was a view that joined 2 tables and I accessed the view the 2 ID fields in the view would still have the AutoIncrement attribute still set to true so that I knew those were Identity fields.



In SQL server 2005

I dont' know why but if you reference a View that has Identiy AutoInc fields in ADO it doesn't keep those properties.



Also for whatever reason we Set the ID field to 0 to let ourselves know its a new Record. SQL 2000 let it happen and assumed it to be null where as By Setting the ID to 0 in SQL 2005 causes it to blow up on me.



Is there some sort of setting in SQL that can make SQL 2005 work like SQL 2000 in these two instances...

View 1 Replies View Related







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