Hello All,
I have a 2-node cluster environment & I am planning to replace it with new hardware. Currently I am using MSA1000 Disk arrays. Now I would like to move my storage to SAN.
What are the necessary pre-requisite and actions to do this. Any particular thing, I must take care in planning.
Any help would be appreciated.
Thanks
Dev
Hi all,
Ok here goes,
I have a three tier system using SQL server 2000, we are currently experiencing IO bottle necks on our SCSI Raid 10 array, which holds the Data and the logs in separate partitions.
So my options as I understand it are:
Get Enterprise edition
or
Get another physical raid 10 array and separate the logs and data i.e. data on one array and logs on the other array.
I would like to try the latter but I am totally unsure how much difference this will make or whether it will make any difference at all.
Does anyone know how much performance increase I will get from using two arrays as opposed to one?
Any other advice on this scenario would be greatly appreciated.
Thanks
hello,all
I am new to Sql 2000,I installed sql 2000 database in C disk,but Now I found my C disk space is smaller than before,So I want to move my databse(include data and structure) from C Disk to D Disk(its space is very large) .
is it possible to do it ?
if its can be done ,do I need to change my asp.net program source code (exp: chaneg my crystal report connectstring ) ?
thanks in advanced!
I'm in the process of migrating a lot of data (millions of rows, 4GB+of data) from an older SQL Server 7.0 database to a new SQL Server2000 machine.Time is not of the essence; my main concern during the migration isthat when I copy in the new data, the new database isn't paralyzed bythe amount of bulk copying being one. For this reason, I'm splittingthe data into one-month chunks (the data's all timestamped and goesback about 3 years), exporting as CSV, compressing the files, and thenimporting them on the target server. The reason I'm using CSV isbecause we may want to also copy this data to other non-SQL Serversystems later, and CSV is pretty universal. I'm also copying in thisformat because the target server is remotely hosted and is notaccessible by any method except FTP and Remote Desktop -- nodatabase-to-database copying allowed for security reasons.My questions:1) Given all of this, what would be the least intrusive way to copyover all this data? The target server has to remain running and berelatively uninterrupted. One of the issues that goes hand-in-handwith this is indexes: should I copy over all the data first and thencreate indexes, or allow SQL Server to rebuild indexes as I go?2) Another option is to make a SQL Server backup of the database fromthe old server, upload it, mount it, and then copy over the data. I'mworried that this would slow operations down to a crawl, though, whichis why I'm taking the piecemeal approach.Comments, suggestions, raw fish?
View 2 Replies View RelatedI'm trying to get a database from SQL2005 to SQL2000. I already recreated the database in SQL2005 and I'm just trying to get some data from just a few tables.
It doesn't appear the DTS or any export functionality is available in my version of SQL Express 2005...so how do I do this. I've tried installing everything I can find.
I've also tried BCP but I keep getting these errors:
SQLState = 08001, NativeError = 53
Error = [Microsoft][SQL Native Client]Named Pipes Provider: Could not open a connection to SQL Server [53].
SQLState = HYT00, NativeError = 0
Error = [Microsoft][SQL Native Client]Login timeout expired
SQLState = 08001, NativeError = 53
Error = [Microsoft][SQL Native Client]An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.
This is a LOCAL database and I have tried -T for trusted, I have also tried a username and password combination. The database is set to Allow Remote connections. Nothing is working.
Can anyone let me know how to migrate the sql server jobs to new cluster server from a stand alone box? Is it easy to just restore the msdb on the new server?
Thanks.
Can anyone tell me how to migrate everything from a stand alone sql server to a new clusterd environment?
1. Master
2. Msdb
3. Model
4. Jobs
5. DTS packages
6. Logins etc.
P.S. I need to move everything from stand alone to cluster.
Can any one tell best way for each of these?
Thanks,
I am having the following problems and scenarios.
I am moving all of our SSIS packages from a stand alone server to a clustered environment. The old server ran Enterprise Edition, the new server runs Enterprise Edition 64 bit.
One package on the new server is giving me the error messaage DTS_PRODUCTLEVELTOLOW when run from a job. The package is stored in MSDB
I went back to the server and ran the following with the following results.
- Connected to SSIS from Management Studio on my desktop and ran the package and got the same error message.
- Did the same as above but was connected to the server through Remote Desktop and it ran fine
- Ran the job, which just runs the package and it ran fine
On the new server it won't run in any scenario.
Any ideas on what to do?
Thanks
I am trying to cluster two sql node server on hyper-v both virtual and my situation is below :
two hyper-v host connected to vnxe storage
two hyper-v are mapped to 3 LUN ( SQL Data , SQL logs , Quorurm)
connectivity between hyper-v and storage direct fiber
three LUN are mapped to the virtual SQL01 and SQL02 as VHDX and configure it on virtual machine as IDE below is the picture
LUNs are presented to the guest SQL01 and SQL02 and visible through disk management
When create the fail over cluster i am not getting the disk to add them to cluster
Getting the below error when validate the storage :
No Disks suitable for cluster disks were found, For diagnostic information about disks available run the Validate config wizard’..
Also , regarding this LUN how i can make them shared on the host side ?
Hello all: looking for some general advice on proper approach. looking to move databases off of a clustered instance to a new (non-clustered) server.
Got several issues i'd like some advice on.
1. This is an OLTP instance that's been around for a while & it's pretty well encrusted with apps & processes that attach to it. Therefore it would be a very good thing if we didn't need to change the connection information in several hundred places after the move.
I've tested one approach to this that seems to work: moved the instance to a server which has the same name as the cluster resource associated with the clustered instance and an instance that has the same name as the clustered instance.
For example: cluster install is aiproddbproduction, moved it to a box called aiproddb with a named instance called "production". There's a bunch of tedious network stuff that has to be done to make this work (binding an IP address to the MAC address of the new box and some murky DHCP reservation fiddling), but after the network crew got done cursing me it did finally work.
Does this seem like a reasonable approach?
2. What's the best way to transfer security info to the new instance? I used the transfer Logins DTS widget but had some problems with it not being able to find some groups in AD.
3. what's the best way to transfer DTS packages?
4. is it necessary for the new instance to be at the same patch level as the old instance? the old clustered instance is still at SP3 and i threw the latest SP4 on the new location. good/bad/indifferent?
5. i was planning on taking a full backup & restoring it to the new machine. Is there a better way? Is the wizard for copying databases a good thing?
Those are these issues i'm aware of and have given some thought to. There are probably things about this i haven't considered and would appreciate some word on.
thanks,
Garth
Is there a way for multiple SQL 2005 instances in a cluster to share drives for user databases.
Once we install our instances in the cluster using seperate disk resources. Can we then have multiple instances share the same physical disk for user databases only. This is for a test environment.
Thanks
Can we backup a DB from SQL Server 2012 (Ent. edition) two node cluster to a local disk ?. Is it possible ?
View 7 Replies View RelatedHello All,
I recently learned of the DiskPart.exe tool that is used to improved the performance of Exchange 2003 cluster implementations. The articles I read alluded to the fact that improperly align disks could ruin the phisical devices themselves due to stress.
So my question is:
How come the MS documentation does not suggest using "Disk Partitions Track-Aligned" methods to improve SQL?
Is there some big difference in the way these two server suites managed I/O reads/writes?
- Rashad Rivera
www.omegusprime.com
I have two Windows 2000 servers (Advance Edition) to form a Windows Cluster. I also install MS SQL 2000 Enterprise Edition on the cluster to form a MS SQL cluster. Now, I want to upgrade the hardware and OS (but keep on using SQL 2000), so I install Windows 2003 server Enterprise Edition on two new servers to form a new Windows Cluster. I am planing to install MS SQL 2000 Enterprise Edition on the new cluster, so the old SQL cluster and new SQL cluster are side by side. I would like to know how to setup a new SQL cluster (I know it has problem to rename SQL Cluster name, so how to fix this problem)? And how to transfer everything (such as system databases, users database, sql user account, password and maintenance plan jobs etc) from old SQL cluster to new SQL cluster? And how to switch over from old SQL cluster to new SQL cluster?
Thanks a lot !
I'm getting ready to install SQL Server 2005 Enterprise for the first time and I have a question about the directory location of the log files and the data files. I have 3 RAID arrays on my server, 1 for the OS, 1 for SQL Logs, and 1 for SQL Data.
Here's my issue. I want to install the logs on the Log array and the SQL data on the SQL data array, however, during the installation I can't find anything that allows me to select certain directories!
Am I missing something somewhere?
Thanks
Hi,I have developed an application using VB 6 (SP 5), MS Access 2000 andCrystal Reports 9. I migrated from from access to SQl Server 2000.This wasn't a problem as i could import all the tables to SQL Server.Also, i could make VB6 talk to SQl Server.The problem arsies when i run my application. The sql syntax foraccess seems to be different than that for SQL Server. A simpleexample being: In access boolean datatype is true/false ,whereas inSQL Server the boolean equivalent is bit (numerical 1 or 0). Thesekind of issues are causing problems and most queries don't run.Would i need to go and change all the queries in accordance with SQlServer syntax ,which would be very time consuming or is there anyfunction which will convert the access datatype into its equivalentSQl Server datatype??Any input/thoughts/suggestions would be appreciated.ThanksJatin
View 1 Replies View Related
Hi
I am having some teething problems while installing SQL on a 3 node cluster. Within the Cluster configuration I have 3 Cluster Groups with each of them having their associated disk resources. All these disk resources physically exist on a SAN.
The actual cluster is running absolutely fine and I can access all the disks from their respective owner node. The problem only starts when I start installing SQL Server 2005 on this cluster. I specify the Cluster group from the Cluster Group Selection and choose the desired partition and then the error message pops up
"There is not enough diskspace on the destination disk for the current SQL Server data files. To proceed, free up disk space to make room for data files, or install the data files to a different drive"
But the disk I am trying to install it on is 264Gb and none of it is used. I have also tried to change it to a different disk within the same Cluster group but to no avail. I have even tried to install it in a different cluster group all together but I get the same error message.
I have googled around havent found anything so far. The disks have got full permissions for the account I am installing SQL with.
Any help will be much appreciated.
Regards
Adnan
i have computer with windows 2000 an sql 7.0 (computerA)
goal is windows 2003 with sql 2005
I see my choices as is:
A) upgrade win2k to 2k3 then upgrade sql7 on w2k3 to sql2k5 on win2k3.
(i see many potential problems with that)
B) have computerB with clean install of win2k3 and install sql2k5 on it.
if this is the case, what is the best / easiest way to get the database from 7 to 2k5? Database copy wizard? dts? attaching the db?
Anything else I should lookout for ?
thnx,
vext
Hi,I've got a database that needs to migrate from SQL 6.5 to SQL 2000. I'mhaving problems with Datetime data types. In SQL 6.5 the Date is shown as'Mar 23 2004 12:00AM' but when I've copied the database across to SQL 2000,although it's still a Datetime data type, it is displayed as '2004-03-2300:00:00.000'. Unfortunately it means Stored Procedures called through afront end Visual Basic application do not work.Colleagues have suggested checking the collation, which I did and it's thesame as the older 6.5 database. Is there another property that needs to bechanged to allow the new Datetime dates to be shown in the desired format?FYI I have Systems Administrator privileges on the older 6.5 database butnot on the new 2000 one.I'm hoping there must be an flag/option I can change. Any help would begratefully appreciated.Kind regardsRich
View 1 Replies View RelatedHi
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
We are about to migrate just over 30 databases from a SQL server 7 installation to a SQL 2000 on a different server. Each database has it's own logins.
What is the best, and most fool-proof path to take? I know from previous experience that restoring a single database works fine, but that the logins are orphaned. Are there complications with restoring the master database from the SQL 7 machine on the SQL 2000 machine? Any advice would be helpful as this is bound to be a painful process. ;-)
Thanks!
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.
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
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!
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
Hi Friends,Is there any tool or assistant to upgrade SQL 2000 to SQL 2005.Thanks,Arunkumar
View 2 Replies View RelatedI am upgrading our SQL 2000 Server hardware. I am looking for a way to "mirror" this server. The only items that we are changing are updating the hardware and the OS will be Server 2K3 instead of Server 2k
Does anyone have a reliable method, or suggested processes for migrating one server to another?
I would like to find out what the steps are to migrate a 2000 database up to 2005?
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 RelatedAny suggestions on migrating Access97 tables to sql server 2000? The DTS seems cumbersome and the Access97 upsizing wizard add-in is only compatible up to sql server 7.0.
Thanks
Hi all
I try to migrate sybase to SQL Server 2000, but found a los of trouble, please, some can help me to resolve this???
May many of that are easy to resolv, but is mi fist time with SQL Server 2000... plz, help :(
Object : Procedure
Error : Sintaxis incorrecta cerca de la palabra clave 'cursor'.
Code :
Create Procedure ABA_CenResul
as
Begin
declare @EST_CEN_Codigo char(8),
@EST_CEN_Descripcio char(100),
@n char(100),
@name char(100),
@salida char(8),
@vble int,
@ini int,
@ter int,
@indice int,
@aux_descripcion char(100)
declare sonido cursor
for
select EST_CEN_Codigo, EST_CEN_Descripcio
from EST_CenResul
open sonido
fetch sonido into @EST_CEN_Codigo,@EST_CEN_Descripcio
select @EST_CEN_Descripcio = @EST_CEN_Descripcio + " "
select @aux_descripcion = @EST_CEN_Descripcio
while @@sqlstatus !=2
begin
select @indice = 1
while @indice <> 4
begin
select @vble = patindex("% %",@EST_CEN_Descripcio)
select @ter = @vble - 1
select @name = substring(@EST_CEN_Descripcio,1,@ter)
if @indice = 1
select @n = @name
else
select @n = @n + "/" + @name
select @ini = @vble + 1
select @EST_CEN_Descripcio = substring(@EST_CEN_Descripcio,@ini,100)
select @indice = @indice + 1
end
print @n
exec sdxsrvr...soundex @n, @salida out
update EST_CenResul
set EST_CEN_Soundex = @salida
where EST_CEN_Codigo = @EST_CEN_Codigo
fetch sonido into @EST_CEN_Codigo, @EST_CEN_Descripcio
-- select @EST_CEN_Descripcio = @EST_CEN_Descripcio + " "
-- select @aux_descripcion = @EST_CEN_Descripcio
end
close sonido
deallocate cursor sonido
end
Thnx in advance
Hi
I am trying to migrate my database in Oracle 8i to Sql Server 2000 but am unsure of how to carry out the migration. How do I do it and what do I have to consider. My OS is Windows 2003. Thanks in advance
I'm changing servers and want to copy all the logins from the old server to the new server. Is there anyway to do this?
View 5 Replies View Related