Hello
I want make log shipping between a Sql Server 2000 64 bits itanium (primary server) and a SQL Server 2005 32 bits.
Is it possible or I'll have got any problem?
Thanks you
I've a 32 bits application that runs on 64 bits Windows Server+MS-SQL.
I've created an ODBC DSN using c:WindowsSysWow64odbcad32.exe.
Sp, the program recognize the ODBC but having problem connecting.
The error look likes this:
***
[Microsoft][ODBC SQL Server Driver][SQL Server]Could not find server '<name>' in sys.server. Verify that the correct server name was specified. If necessary, execute the stored procedure sp_addlinkedserver to add the server to sys.servers.
***
Any help is appreciated.
Regards,
Ben
Hello,
This is my first post in this forum, I have one application built in asp .net, through a ODBC connect to a external database (prinex). The application was running in a 32bits server, but the server had to stop and now there is running in a machine of 64 bits.
The driver that use in server of 32 bits only exists for this version, right now i have to use the same for the 64 bits machine, i can install and configure the DSN (using c:WindowsSysWow64odbcad32.exe).
But at the time of execute the aplicattion an error is displayed. ¿How can i solve this problem?, ¿There is a way to force the application to use 32 bits DSN? ¿There is an alternative solution for connect to the database? ¿Someone had the same problem?
This is the image of the error:
http://img404.imageshack.us/img404/8168/errorwebbn1.png
If somebody can help me, i would be very grateful.
PD: Sorry for my english.
Hello,
I am setting up a new server with Windows Server 2003 x64 bits and SQL Server 2005 x64 bits. Under 32 bits of Windows we normally use /3GB and enable AWE under SQL Server (both SQL 2000 and SQL 2005) and allocate 6 GB of fixed memory to SQL Server.
Does any one know whether I should do the same thing under the x64 bits platform. I read some articles on the web that it is no longer required to use AWE under SQL 2005 x64 bits??
Please advise.
Thanks.
Hello,
I'm trying to install a version of SQL server 2005 with reporting services on a vista 64 bits.
I've a licence for SQL server 2005 standard edition in French, my vista is in French, and I'm using visual studio standard edition in English to develop. I would like to develop reports using SQL server to include these reports in my applications developped with Visual Studio.
Wich version of SQL server should I install ? I've tryed to install SQL server express 2005 with advanced feature SP2 (english version) and then later the standard edition (French version) (each time uninstalling all SQL server components between tries), but I got problems with reporting services each time.
I got first a warming saying than reporting services is 32 bits and IIS is 64 bits, I so allowed IIS to run 32 bits ASP .Net, but after that, I now get a problem of .Net registration in IIS as warming message on the line concerning Reporting services during the install of SQL Server, and it doesn't even offer to install RS on the next window.
I reinstalled the DotnetFX64 to be sure, but still get the same message. If I look in the IIS the application pools are looking me to be normal, with the ASPNET 32 bit code allowed.
Hi,
Does anybody know if the SQL 2005 express edition works on Windows Server 2008 64-bits?
Many Thanks.
Hi,
I have an vendor application need to use SQL Server 16 bits version for server and client. I installed the SQL Server 6.5 from my "Backoffice 20" CD ROM
I was told that after my installation of SQL Server 6.5 on server, if there is a folder "BIN" and "BINN", that means that I have installed both the 16 and 32 bits version. Is this true? To install SQL Server Client, if I install from my server from the sql65i386, the 32 bits client will be installed to my client workstation. Which folder should I look for the 16 bits client installation?
Hi,
I developed an SSIS package on my computer (32bits).
The package basically get data from excel file and save it to a sql database.
I use an OLE DB connection to the excel file:
Provider=Microsoft.ACE.OLEDB.12.0;Extended Properties=Excel 12.0;
other info: Run64bitRuntime : false
It works fine on my local computer.
I use the DeploymentManifest to deploy the package on the server. (all validations are ok).
But when I run a job which run the package i get this:
with job step : SQL Server integration Services Package:
Executed as user: LU1xp_cmdshell. ...on 9.00.3042.00 for 64-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 10:29:04 AM Progress: 2008-03-06 10:30:20.22 Source: Data Flow Task
Validating: 0% complete End Progress Progress: 2008-03-06 10:30:20.26 Source: Data Flow Task Validating: 3% complete End Progress Progress: 2008-03-06 10:30:20.29 Source: Data Flow Task Validating: 7% complete End Progress Progress: 2008-03-06 10:30:20.32 Source: Data Flow Task Validating: 10% complete End Progress Progress: 2008-03-06 10:30:20.35 Source: Data Flow Task Validating: 14% complete End Progress Progress: 2008-03-06 10:30:20.35 Source: Data Flow Task Validating: 17% complete End Progress Progress: 2008-03-06 10:30:20.35 Source: Data Flow Task Validating: 21% complete End Progress Progress: 2008-03-06 10:30:20.35 Source: Data Flow Task Validating: 25% comple... The package execution fa... The step failed
With job step cmd system:
Executed as user: LU1xp_cmdshell. Microsoft (R) SQL Server Execute Package Utility Version 9.00.3042.00 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved.
Started: 10:32:37 AM Could not load package "******" because of error 0xC0010014.
Description: One or more error occurred. There should be more specific errors preceding this one that explains the details of the errors. This message is used as a return value from functions that encounter errors. Source: Started: 10:32:37 AM Finished: 10:34:08 AM Elapsed: 91.141 seconds. Process Exit Code 5. The step failed.
No more detail about the error.
There is something strange:
When I execute the package via DTEXECUI on my local computer and i speciify the sql server where i deploied the package. It works.
The same on the server doesn't work.
I don't get it.
I suppose this is more an RFC than a true question, but I've come to realize "bit" data types do not optimize a query when they are used in a WHERE clause. Since they cannot be indexed, it forces the analyzer to query an available index for rows based upon the non-bit constraints. The result is then scanned to match the values of the bit constraints of the query. So you're potentially doing a full table scan, or an index scan.
My original thought was that I'd improve performance by using bit fields since they are a smaller datatype, but as development progressed, we began using those bits in our queries. At this point, it may be beneficial to convert those bit types to smallint.
Am I wrong in my conclusion?
Hi all,
View 3 Replies View RelatedHow may extra bits does a NULL column contain.And how many extra bits does a varchar column contain.(I 've worked with Ingres and in that environment it both needed 2 extrabits)Bye,Arno de Jong, The Netherlands
View 2 Replies View RelatedHi,
View 10 Replies View Related I have an Application developed on ASP, I got a few new servers 64bits, I installed microsoft WIN 2003 SR.
When I get in into the web site I receive this errors:
Microsoft OLE DB Provider for ODBC Drivers error '80004005'
[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified
/ConnectToDatabase.asp, line 17
I made some obvios checks, I checked that the ODBC really exists and we move the IIS 6.0 to run in 32bits mode as I found in some page.
Thanks you.
Ahmed
I work for a small state government department. We are about to install SQL Server 2005.
A national government department that runs on SQL Server 2000 are willing to give us a backup of their database (20 gig I think) and then log ship to us regulary. Our aim is to have a copy of the database that we can query from and that is only a day or so out-of-date.
I'm having no luck.
1. I can backup the SQL Server 2000 database.
2. I can restore the SQL Server 2000 database onto the SQL Server 2005 box no worries.
2. BUT, if I attempt to restore the 2000 database with the option 'Leave the database in read-only mode ...' selected (so that I can then restore transaction logs and it's read-only), then I get an error message. ""This backup cannot be restored using WITH STANDBY because a database upgrade is needed. Reissue the RESTORE without WITH STANDBY.". I'm doing all this using SQL Server Management Studio.
It appears we will have to use SQL Server 2000 rather than 2005 to get this working.
Q: Has anyone successfully done this from SQL 2000 to SQL 2005 please? If so, how was it achieved please?
Thanks.
------------
Robbie at 3/7/2002 10:13:00 AM
Great news but how??
------------
mmwops at 3/7/2002 9:09:32 AM
can be done
------------
Robbie at 3/7/2002 7:03:16 AM
Does anyone know if Log Shipping be done using SQL Server 2000 standard edition or does this have to be Enterprise??
Many Thanks
Robbie
Hi,
I have maintanance plan for log shipping.it was working fine for last 2 months.But due to some reason I have to restart the server and after that my log shipping job was failed.When I start the job it is showing error "Executed as user: OKS-MARAdministrator. Invalid drive specification 0 File(s) copied. Process Exit Code 4. The step failed".This error is coming when I copy the bakup database file to another server.I have checked all the mapping and sharing option.Also I have nt changed anything in the two servers.But still then the error is coming.
Can you please help me out to shot out the problem?
Thanks in advance.
Sunanda
hi,
i have log shipping between 2 servers on sql server 2000. the log shipping failed because of some problem with transaction log backup files. somehow the files are missing and it is not able to apply transaction log. can someone please tell me how can i restore the log shipping between 2 servers. please help asap..need to fix it in couple hours
Hey all-
I am working to establish a backup plan for SQL Server 2000. We are currently doing log shipping between servers.
A full backup once a week
transaction log backup every hour
We run a bulk deletion (delete * from table where date < ninetydays) which deletes 22,000 rows approximately. We are running in Full Recovery mode.
I wonder if there was anyway to improve my backup plan, preferably minimizing logging when the deletion takes place but still backup the data with log shipping.
Let me know if any of you have ideas. Thanks
Nate
I am in the process of migrating from Sql Server 2000 to 2005. Part of my plan is to move some database's to 2005, but use the 2000 compatibility mode for the short term. My issue is this, our DR boxes are still on SQL Server 2000, would I still be able to use our log shipping processes? Or would I be better off in starting with migrating the DR boxes to 2005 first?
Thanks in advance.
We have an environment where 3 SQL 2000 servers exist; one production servers and two standby servers that receive logs via log shipping. Everything works fine and it is stable. My client wants to get a new 64 bit server and run SQL 2005 64 bit version for the production box. Can we still do log shipping with the two remaining SQL 2000 boxes or do they all have to be on the same version and bit version?
Thanks
Bill
I have set up log shipping between two servers with a third serving as a monitoring server. Recently the monitoring for the eight databases that I am log shipping began to indicate that everything was failing. Upon further inventigation of the log_shipping_monitor_history_detail tables on the prinary and secondary everthing appears to working properly but I have been unable to resyncronize the monitoring. I have attempted to use the stored procedure sp_refresh_log_shipping_monitor to no avail, it does not appear to do anything with respect to the data in the dbo.log_shipping_primary_databases and log_shipping_monitor_primary tables on the primary server or the log_shipping_monitor_secondary and dbo.log_shipping_secondary_databases tables on the secondary. I have also manually updated the records in these tables in an attempt to syncronize but after the next sucessful backup, copy and restore this monitoring data is not updating. Does anyone have any ideas as to what I am doing wrong or how I might rectify this situation.
View 3 Replies View RelatedI am getting the following error " The specified servername does not exist" when I run the Log Shipping procedure. There is only a Primary server running Win Server 2003 withe Service pack 2 and SQL Server 2005 with service pack 2 and one secondary server runnung Win Server 2003 R2 with service pack 2 and SQL Server 2005 with service pack 2. All permission setting look ok . Can anyone help
View 4 Replies View RelatedI have installed SQL Server 2005 and setup a cluster and log shipping. I decided to perform a planned failover and realized that there are no sp_change_primary_role and sp_change_secondary_role stored procedures. I checked on both the SQL Server 2005 installations and could not find them.
My question is :
"Is it safe to get these stored procedures from a SQL Server 2000 database and run them on the SQL Server 2005 database ??"
"Has anyone come across such missing stored procedures in SQL Server 2005 and know the reason why it is so (so that I can avoid it in the future if it due to a faulty installation) ?"
Cheers
NEVILLE GEORGE
Hello,
I would like to know if anyone has a recommended method for having backups to tape while running log shipping. For example, is it possible to copy the transaction log backups used for log shipping to tape and apply them to a Full Database Restore from a 3rd Party Backup tool such as Veritas?
My goal is to be able to do a point-in-time restore from tape and still be able to use SQL Server 2005 Log Shipping.
Thanks,
Erik
Afternoon,
I have a few Log Shipped DBs that are working great.
Currently they are set to fire off every 15 minutes 24/7.
My question is this ... I need to get FULL backups of the source DBs in order to restore them on certain Dev boxes.
If I were to execute the full backup on one of these Log Shipped DBs ... how would it affect the log shipping process?
Is there a special method to accomplish this?
As a side note, what would be some concerns/issues if in being able to create the FULL backups and not interupt log shipping, I were to create the backup using a 3rd party tool like Quest LiteSpeed?
I sure wish we were on Enterprise, then I could create a mirror and then snapshot off it to create my backups BUT ... that is not the case as we stand today.
Thanks
My server is a dual AMD x64 2.19 GHz with 8 GB RAM running under Windows Server 2003 Enterprise Edition with service pack 1 installed. We have SQL 2000 32-bit Enterprise installed in the default instance. AWE is enabled using Dynamically configured SQL Server memory with 6215 MB minimum memory and 6656 maximum memory settings.
I have now installed, side-by-side, SQL Server 2005 Enterprise Edition in a separate named instance. Everything is running fine but I believe SQL Server2005 could run faster and need to ensure I am giving it plenty of resources. I realize AWE is not needed with SQL Server 2005 and I have seen suggestions to grant the SQL Server account the 'lock pages in memory' rights. This box only runs the SQL 2000 and SQL 2005 server databases and I would like to ensure, if possible, that each is splitting the available memory equally, at least until we can retire SQL Server 2000 next year. Any suggestions?
When I proposed start to use SQL Server 2005 for new VS 2005 web sites, one of my co-workers responded that
we will update the old SQL Server 2000 databases to SQL Server 2005 when we are ready to use 2005 SQL Server.
Questions:
1. Any expected problems to upgrade old 2000 databases to new 2005 SQL Server?
2. I have installed both 2005/Management Studio Express and 2000/Enterprise Manager in my PC. Any expected
problems when running both 2000 and 2005 SQL Server at the same database server?
3. What is the best configuration for running SQL Server 2005 when we have old 2000 databases? Upgade or not upgrade?
TIA,
Jeffrey
Hi
We would like to install Sql 2005 Enterprise Edition (including database engine, reporting service, integration service and analysis service) as a sepearte instance on a server which already has Sql 2000 with reporting services and analysis services. We do not want to disturb the existing sql 2000 setup.
If we do that then what will happen to my earlier sql 2000 reporting service? Will it be upgraded to sql 2005 reporting service? I heard that reporting services are instance unaware application. Where will be the default reporting service database available?
Please help us.
Regards,
Sankar N
When I try to migrate a database on a SQL Server 2000 server to a SQL Server 2005 server with the Copy Database Wizard of the SQL Server Management Studio, I'm confronted with the following problem;
Performing operation...
- Add log for package (Success)
- Add task for transferring database objects (Success)
- Create package (Success)
- Start SQL Server Agent Job (Success)
- Execute SQL Server Agent Job (Error)
Messages
* The job failed. Check the event log on the destination server for details. (Copy Database Wizard)
When I take a look at 'Event viewer' on the SQL 2005 server, the following error is displayed;
InnerException-->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.
(provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
I already enabled the MSSQLSERVER network configuration protocols (TCP/IP and Named Pipes ).
How do I solve this problem?
Hi,
We have an old machine which holds SQL server 2000 database. We need to migrate a whole database to a new machine which has SQL server 2005.
When we tried to move whole database using Import and Export Wizard, only tables can be selected to import/export. However we want to import/export the whole database, including tables, stored procedure, view, etc. Which tool should we use?
Thanks.
Hi,
We have an old machine which holds SQL server 2000 database. We need to migrate a whole database to a new machine which has SQL server 2005.
When we tried to move whole database using Import and Export Wizard, only tables can be selected to import/export. However we want to import/export the whole database, including tables, stored procedure, view, etc. Which tool should we use?
Thanks.
Hi Guys,
I have had SQL Server Express and Sql Server Management Studio Express installed on my machine for some time and recently tried to install a trial of SQL Server 2005 as well. (Yes, I'm migrating from Visual Studio Express to Visual Studio Professional, just as in tended!)
Everything went fine except that nothing seemed to be installed. I searched in all the obvious places - both on the Start/Programs menu and on the hard-drive: nothing.
A check under Add/Remove Programs showed that Sql Server 2005 Express was installed, but called SQL Server 2005.
So after a number of retries in which the install program kept saying that there was nothing to install, I selected every option under Advanced in the intall process. This resulted in stuff being installed and I now have SQL Server 2005 running on my machine, but no SQL Server Manager icon.
My questions are:
Where can I find the SQL Server Manager executeable?
Has anyone installed SQL Server Express, SQL Server Mangement Studio Express, SQL Server 2005 and SQL Server Management Studio on a single machine successfully? If so, what order did you install them in? (I'm planning on uninstalling everything SXQL Server related and starting again.)
Thanks very much for your help.
Regards
Gary
Hi
I have created a linked server from SQL Server 2005 (SP 1) to SQL Service 2000 (SP 4) with a sql server login that is available on both servers but with different passwords and permissions.
I am getting the following error while accessing the linked server in management studio based on the scenario given below ;
------ Error Message Starts
OLE DB provider "SQLNCLI" for linked server "(SQL Server 2000 instance name)" returned message "Communication link failure".
Msg 10054, Level 16, State 1, Line 0
TCP Provider: An existing connection was forcibly closed by the remote host.
Msg 18456, Level 14, State 1, Line 0
Login failed for user 'abc'.
------ Error Message Ends
Consider login name is abc.
Now this login abc has sysadmin rights on sql server 2005.
The same login abc has only db_datareader rights on sql server 2000 on just one database and is not associated with any fixed server role.
I have configured the linked server using the following options;
1. I have tried impersonating login from SQL Server 2005 to SQL Server 2000 .
2. I have also tried specifying remote login / password option.
Anyone having any idea, would be of great help.
Regards,
Salman Shehbaz.