We have setup SQL Server 2000 32-bit (Publisher/Subscribers) replication with 5 different locations. We are planning to purchase SQL Server 2005 Enterprise Edition 64-bit and/or 32-bit. I need suggestion, if we have both version of 2005 Enterprise, can we setup replication with SQL Server 2005 64-bit with SQL Server 2005 32-bit? is that supporting?
Also can we run replication with SQL Server 2005 64-bit (Publisher) with SQL Server 2000 32-bit (Subscriber).
My asp.net website is using sqlexpress2005. I am planning to use sql2000 with this existing website. My questions:
1. How can I transfer the database definitions and actual data from 2005 to 2000? is this possible? 2. What if I have exisiting database in sql2000, can I convert it to be used in sql2005? 3. should I manually recreate the database when converting from one version of sqlserver to another? and how abt the actual data?
I work on the Clinical Surgery Department Data Application. The patient gets through the Admission, Surgery, PostSurgery and Discharge stages during his staying in the department. The Doctors just insert their medical data in to the different tables. I have three main classes: User, Patient and Portfolio ( patients portfolio ) and all the business bases on these classes. The problem is with the Classes per Medical Data Tables. The Medical tables should exist cause it includes the medical data about the patient however what is not clear: Whether I should create Business and Entity classes per each medical data table ( and this is something like 50 tables ) or I should insert all the functions in the Portfolio class and then there will be a mess of functions in one class? What is the accepted way to perform it ?
We were having problems setting up the mirroring, so I did it via command lines. I found out the "alter...set partnership" command works on the mirror server going to the principal, but gets a 1418 error when going from the principal to the mirror. So if A is the principal and B is the mirror, A to B fails but B to A works. If I reverse it so that B is the principal and A is the mirror, B to A fails and A to B works. Any suggestions?
Is there any equivalent function in T-SQL (SQL Server 2014 / SQL Azure)?
Specifically, I want to be able to convert a time into UTC before inserting it into a table. Right now I am doing:
INSERT INTO Incident (IncidentDescription, dtOccurred) VALUES (@IncidentDescription, DATEADD(hour, 8, @dtOccurred))
I don't want to hardcode "8" and I want it to adjust for daylight savings time (DST).
Is there any concise solution that does not require me to define SQL functions or have lookup tables? I also don't want to use the difference between GETDATE() and SYSUTCDATETIME(), because the timezone of my server is not my local timezone.
If I join Table1 to Table2 with a WHERE condition, isit the same if I would join Table2 to Table1 consideringthat the size of the tables are different.Let's assume Table2 is much bigger than Table1.I've never used MERGE, HASH JOINs etc, do any ofthese help in this scenario?Thank you
1. Is it possible and what would be the gotchas for taking a backup of a database in a 32 bit instance of sql server 2000 and loading it into a 64 bit instance of 2000? How about 2005 to 2005?
2. Is it possible to reverse that and go from a 64 bit to a 32 bit?
3. How about going from a 32 bit sql server 2000 into a 64 bit sql server 2005?
We're on the verge of upgrading a rather large database from sqlserver 2000 (32 bit) into 2005 (32 bit) but they anticipate eventually upgrading the hardware to 64 bit at least for production. The test node would remain at 32 bit. Thanks for any help.
I have a pretty large DB and a fairly complex query. If I drop buffers and clear cache the query runs in 20 seconds returning 25K rows. Subsequent runs are 2 seconds. Is this the result of the results being cached, execution being cached, other? Are there good ways to close the gap between the initial and later runs? Does the cache stay present until the service restarts or does SQL recycle the memory and if so, based on what criteria?
Does anyone know what SQL Server uses to identify other servers which contain SQL Server, when you attempt to register a new server through enterprise mgr? For instance when you go through the new sql server registration wizard, the second screen allows you to choose what server you would like to register, and it shows you the available servers on the lan that contain sql server 6.5 or 7.0. What is enterprise mgr using to locate the other servers containing SQL Server? Thanks in advance.
I just created a new db on a programmer's machine. Now I cannot register his sql server on my sql server. It doesn't like 'sa'. I can connect as 'administrator' but then I cannot do anything. Seems like the logins are messed up. I am not able to execute any stored procedures as administrator.
I have recently installed SQL Server 2000, And trying to register a remote SQL 7 server, through enterprise manager which fails with the following error message: Timeout expired
I am able to connect to the same server using Query Analyzer. I was able to register this server from the same machine, prior to the installation of SQL 2000. Also, I am still able to connect to other SQL 7 servers, with SQL 2000 enterprise manager.
Over the weekend we changed ISPs on our SQL Server 2000 machine. The only configuration change was the IP address. I'm able to register the server from client machines using EM which are on the same network, but I can't register it from home. I've verified the IP address, username/password etc and the connection just fails with the message 'Sql Server does not exist or access is denied.' Could this be a port issue? Any ideas? Thanks.
Please pardon my ignorance, but I am using MS SQL2000...On system start upthe Server Service Manager defaults to server "BACK" which is not evenregistered in the SQL Enterprise Manager. Enterprise Manager shows only oneserver " OFFICE" which is the one I want to default to. How do I remove the"Back" server completly from the system?thank you
Ok, well I just installed Visual Studio.NET 2003 on my PC, and to prepare for next years courses I thought I might get going on some of the exercises. But I am rather new to this and when I try to expand "SQL Server" in the "Server Explorer Window" I get this message.
Could not automaticly discover any SQL Server instances. Choose Register SQL Server instance from the shortcut menu if you know there are SQL Server instances on this machine.
From there all I know is that I can right click on "SQL Server" and chose register new instance, but I do not know what to enter, and it suggrests leaving it balck but that doesn't work. I will get an instance but when I try to expand it another error pops up.
So as you can see I have no idea what I am doing when it comes to SQL Server, can any one help me with this?
hi, I have just installed Ms sql 6.5 and tried to register the server, I typed a name and did not get any response. This installation was on a single pc which is not connected to the network... any idea of why the server is not responding. Do I need to give a name to the pc before I installed the sql server and then use register the server...
Hi all, I have installed SQL Server 2k personal ed on Win xp and now I want to add another instance other than that one I added when installation.But I do not know how? I used EM and its wizard but it says could not find server or access is denied... -any quick help is appreciated
I am trying to register a SQL Server 2000 on a client machine. It was workig fine , until yestarday when he moved and got a different system IP. But one of the SQL Server 'A' is getting connected. But when I try to register the server 'B' its giving an error " SQL Server does not exist or access denied". I am giving correct login credintels. When I tried to ping ( using cmd) the Server 'B' , the system was able to connect.
Hi all,We have standardized on Hyperion as our reporting tool. So far I haveonly set up a couple of Access databases as data sources for it. Nowthere is a request to report off our eOn (telephony management) SQLServer database using Hyperion. The eOn SQL Server box is in aworkgroup that is not part of the rest of our domain. (We only haveone domain because we don't have a "forest", whatever that means.) Itis behind a router owned by eOn along with a PBX and some other stuff.Setting up a data source for Hyperion requires creating a special datasource file called an .oce on the box where the Hyperion fat client(required for most administrative tasks) resides, and also setting up adifferent special data source file called a .das on the server wherethe Hyperion services run. (The analysts and end-users do not have thefat client, their access is web-based.)I have to register the eOn SQL Server by using the IP address and SQLServer authentication. (I was told that I can't use Windowsauthentication because it is not in the domain.) From the box onwhich the Hyperion fat client resides, I cannot register the eOn SQLServer. The error message is "timeout expired". Tracerting indicatesthere are no intermediate hops when attempting to connect from thisVLAN. From my desktop, which is on a different VLAN, I can connect toand register it. This trip includes one hop at our 6509. From one ofmy servers which is on the same VLAN as the fat-client box, I am ableto connect and register. On the fat-client box I tried deleting andre-registering another SQL Server and there was no problem.The IP address I have to use to connect to the eOn SQL Server is *NOT*the actual IP address of the box it resides on, but rather the eOnrouter, which translates it to the address of the server. We have nocontrol over this, eOn creates this setup. I'm not sure how it knowswhich of the devices behind it a given message is for.Ideas?
I was on the SQL Server Express Edition site (http://www.microsoft.com/sql/editions/express/default.mspx), and I used a link that suggested by registering my SQL Server Express I could get some royalty free images and an e-book. I followed the process, and they immediately sent me an email full of links, some of which do not seem to work. The link for the Registration Benefits Portal takes me to a "Page Not Found" error on Microsoft. The article within Resources called "Using SQL Server 2005 Reporting Services with SQL Server Express" also doesn't work.
I guess I didn't really need these "benefits", but it was kind of aggravating. This is 10 minutes I won't ever get back.
Since the email said to report any problems to the forums, this is what I am doing.
I have set up SQL Server Express with a Server Name / Instance name RMUKOCSQLEXPRESS
However, from another Server running the full SQL Server 2005 Management Studio I cannot seem to register the above Server. The usual message of : "An error has occurred while establising a connection to the server...."
I have allowed remote connections, set up default, named pipes etc on the SQL Server Express. Yet from the SQL Server Express Management Studio I can register full 2005 Server / Instances but not the other way round.
Is there anything else I need to be aware of or check for.
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) (Microsoft SQL Server, Error: 53)
When I try to regiter a sql server, I take this error message. I am using Sql Server 2005. What is the problem,can you help me?
I am running SQL 7 (SP3) on a 2000 Server. When I configure the server as part of the Workgroup I have no problems connecting from the workstation. However, if I join the server to our 2000 domain, I cannot connect and/or register the server from the workstation through EM.
Is this a security issue? If so, what are the minimum requirements or what else am I missing. Any suggestions would be appreciated.
We are running 3 versions of SQL - 6.5, 7.0, and now 2000. I have all three versions installed on my PC and run Enterprise Manager to manage the 2000 and 7.0 servers. The one 7.0 server is registered fine. When I try to register the other 7.0 server I get the following message -
(SQL DMO) SQL Server xxxx must be upgraded to version 7.0 or later.
This same server is registered through Enterprise Manager on another PC running the 3 versions of SQL and both SQL 7.0 servers work fine on that Enterprise Manager installation.
Any suggestions as to what I need to do to be able to register the 7.0 server on the Enterprise Manager running on my PC?