I am having issues after installing SQL 2005 together 2000.
SQL 2000 is working without issues, then I installed 2005 with a new instance so I did not lost my SQL 2000. After the installation has finished, I rebooted the server and when I want to open "SQL Server Management Studio" menu of SQL 2005, this menu is not present. I uninstalled SQL 2005 again and perform an installation once again but this menu isn't present. (Now, SQL 2005 is uninstalled). Even more, I compared the folders created for SQL 2005 in another server and they are different. Seems that the installation is not complete... Can be?
What should I review?
Any help is greately appreciated!!
We have several servers that perform multiple functions (file and print server, SQL 2000 server and WSUS 2.0 server among others). These servers are located in remote locations and are connected across a WAN. We cannot upgrade the SQL 2000 because of an older application that doesn't work with SQL 2005. Currently we run WSUS 2.0 using MSDE and have no problems. I have upgraded our main WSUS server to 3.0 and would like to upgrade these remote servers to 3.0. My question is can the new version of MSDE (Windows Internal Database or SQL Express) reside on the server along with SQL 2000 without causing problems? If I have to uninstall 2.0 and MSDE and then do a clean install of 3.0 that isn't a problem.
Hi, I've went throught the SP4 documentation but I didn't find a clear answer about how to deal with this situation: In the situation of a multi instances server in which all instances are SP3a, can I just upgrade a couple of instances to SP4 and leave the others in SP3a ? . One of the instances I may have to leave in SP3a belongs to a merge replication environnement (Distributor and Publisher), while the Subscriber is also in SP3 on a remote server (which I don't administer..).(the point is that in this situation I have to upgrade the 2 servers simultaneously) In other words, when I 'll apply the SP4 to just one instance, I understood that the all the tools will be upgraded to SP4.
Will the merge replication involving a SP3 instance on the same server still work?
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?
I am attempting to move some SQL 2000 databases to SQL 2005. My main production database does not seem to want to move. When I use the SQL 2005 GUI the .bak backup file is marked 'Incomplete'. When I attempt to restore the backup file I get a 'RESTORE detected an error on page (0:0) in database' message. I saw a thread in the SQL Express forum suggesting trying to restore from the T-SQL level to get the GUI out of the picture and I get the same 'error on page (0:0)' message. However when I take the same file and use SQL 2000 Enterprise Manager it restores with no problems.
Hi, I am trying to edit some data from a SQL2000-datasource in ASP.NET 2.0 and have a problem with a column that has bit-data and is used for selection. SQL2005 works fine when declaring <SelectParameters> <asp:Parameter DefaultValue="TRUE" Name="APL" Type="boolean" /> </SelectParameters>When running this code with SQL2000, there are no error-msgs, but after editing a record the "APL"-column looses its value of 1 and is set to 0. Looks like an issue with type-conversion, we've hit incompatibilities between SQL200 and 2005 with bit/boolean several times before. So, how is this done correctly with SQL2000? (I've tried setting the Type to "int16" -> err. Also setting Defval="1" gave an err) ThanksMichael
Hi,i have SQL 2000 and 2005 on same machine(with different intance names,of course), my laptop - XP with SP2. The 2005 works fine but i can'tconnect on SQL 2000. All the the SQL services are started.Any idea? Have i to reinstall 2000?Tks,Lourival
I have to merge the data from two databases, one is in SQL Server 2005 format, one is in 2000. The merged data will then reside on a SQL Server 2000 platform. Is there an easy way to do this through Management Studio or Enterprise Manager? Or will we have to export the data from the 2005 database to a flat file and import it into a new 2000 database. And then do the merge?
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?
I have several SQL 2000 servers I need to setup transactional (non updatable) replication with. The structure is:
SQL Server 2000 as Publisher/Distributor
SQL Server 2005 Standard as Subscriber
The connection is via the Internet with snapshots using FTP.
I setup the first set (2 databases at location A). They work wonderfully. I created the publication and then subscribed using MGMT Studio for 2K5.
II am setting up the same scenario for location B. Here is my problem:
In MGMT Studio I connect to the publisher (SANDRA). I right-click a publication and choose New Subscriptions..., the publication is already selected. I click next - Run each agent at its Subscriber is selected and the only option (this is desired), I click Next
HERE IS THE PROBLEM:
On the Subscriber's screen there are no Subscribers listed. When setting up location A the subscribing server was listed and I could choose a database. The Next button is greyed out and there is no way to create/add one.
I tried setting up the subscription by right-clicking the subcribing server's Replication folder in MGMT Studio but I get the same result (except that I have to authenticate with the publishing server which works fine).
WHAT'S DIFFERENT:
Location A is SQL Server Standard (SP3) running on SBS2K3. It is obviously on a domain and so SQL Server and the SQL Agent are running under domain accounts. Location B is a Windows XP SP2 machine running SQL Server Personal Edition (it actually says Development Edition in the properties window).
The databases are the same strucutre, different data. At location A the firewall is set to allow 1433->*any* and *any*->1433 where *any* is 1024 or higher. On the XP machine the firewall is set to allow port 1433. I don't think this is the issue because I've turned the firewall off on the XP machine and I get the same result.
Most of our sql servers ar still sql 2000. Our programmers created many sql 2000 database diagrams using EM. But they can not access them under sql 2005. (They now have only sql 2005 tools installed on their boxes.)
Question: can we reinstall the sql 2000 client tools on their boxes without affecting the current sql 2005 install on their boxes?
Question: is there any workaround negating the need to ihstall the sql 2000 client?
I'm trying to connect to Desktop SQL Server 2000 from Windows mobile PC Emulator (VS 2005). I need a direct connection using connection string to SQL Server 2000 through local wireless network without IIS.
Bellow is the code that I use. After executing this code I get an error on line Conn.Open(). Error says SQL Server does not exist or access denied. SQL is un and running, and I can log in using SA username from the desktop. Even if I chance IP for another SQL server in my connection string I still get the same error. There is no firewall of any kind running.
Dim connectionSTR As String = "Persist Security Info=False;Integrated Security=False;Server=192.168.0.202,1433;initial catalog=MyDB;user id=sa;password=;"
Dim Conn As SqlConnection
Conn = New SqlConnection(connectionSTR)
Conn.Open()
If Conn.State = ConnectionState.Open Then MessageBox.Show("Open") End If
About my environment: SQL Server 2000 is running on Desktop PC with Windows XP SP2. Application which I need to connect to SQL Server is in Visual Studio 2005. I execute the application in Windows Mobile PC Emulator and try to connect to SQL Server from emulator.
I would like to ask you if there is better to recreate database structure on 2005 from 2000 and move data or to just load 2000 backup.
Currently I loaded the backup, but I am wondering if there might be slightly better performance on 2005 when recreating structure on 2005 to loading 2000 backup?
Does loading 2000 backup create 2005 binary structure?
How do SQL 2000 service packs play a role in upgrading? That is, can SQL 2000 Standard with no Service Packs(SP) be upgraded to SQL 2005 Standard, or does SQL 2000 Standard have to have a certain service pack??
If we changed the sort order from BIN to BIN2 but kept everything else the same will it have any effect on replication? So in SQL 2005 if I were to change my default collation from Latin1_General_Bin to Latin1_General_Bin2, would that cause replication to break? I suspect that it will not be an issue since it is just sort order that is changing and the code page stays the same.
BTW, this is transactional replication. Sorry, I left that out of my original post.
Hi all.My webhost prepared a server for me with sql 2000 instead of sql 2005.Will my asp.net 2005 application work there?I generated a script to export my sql server 2005 objectsLots of failures appeard.IF NOT EXISTS (SELECT * FROM sys.database_principals WHERE name =N'aspnet_WebEvent_FullAccess' AND type = 'R')CREATE ROLE [aspnet_WebEvent_FullAccess]GOThis is the error:Server: Msg 170, Level 15, State 1, Line 2Line 2: Incorrect syntax near 'ROLE'.The object is part of the asp.net security/login components - I did not create these objects myself!Please tell me what to do next..........TIAGuy
Hi, What would I lose out(functionality wise) if I were to use MS SQL 2000 instead of 2005? What are the main differences, and considerations to be factored in before choose which database to work on?
Hi I'm doing my fierst steps in .net and sql I have made a website base on sql data in sql2005 'and find out that my hosting company (I'm host on shear server ) is only supporting sql2000 how can I convert it to 2000 ? Or is there anther trick? Thanks assaf
i have developed my project in asp.net 2.0 +ajax +c# as backend with sql server 2000 as back end now my question is can i change my sql server to 2005 will it gives any problem in furture all my queries will run properly
HI, I Have my websites developed in sql 2005 and my host is providing SQL 2000. WHAT problem i might face will my site run ? or do i need to change things??
I want to use SQL 2000 with VS 2005. I do have SQL 2005 Express installed but i would rather use SQL 2000 because all my DBs are currently in this version and I want to get up and developing now and then convert them to SQL 2005 one at a time. LATER...When I try to connect to SQL 2000 through VS 2005 I keep getting this error that tells me it can not connect to SQL 2005 Express. This is my conncetion string: Const connectionString As String = "Server=localhost;Trusted_Connection=True;Database=Northwind"One thing that I see wrong with the error is that I thought SQL 2005 did not have Northwind anymore. And 2 this is a sample app from MS website. So why would it try to connect to SQL 2005 Express. This is my first try at connecting to a DB with VS 2005.Please Help.-J
Hi, I am currently developing my website to ASP.NET 2.0 using SQL Server 2005 Express Edition.
However, after long hour to figure out, my hosting company doesn't use sql 2005. They only have SQL Server 2000. Even I have to pay for using SQL 2000.
My question is, what is the different between SQL 2000 and 2005 in term of using it in a server? My condition is that I am developing my database under SQL Server 2005 EE, now, can it be uploaded to be used in a server with SQL 2000?
Thanks in advanced for all help, time and your support. HAVE a good day!
can anyone point me to where microsoft are displaying the product expiry of SQL 2000, ie how soon do we need to be looking at adopting the new version?
We are starting a new project and for production we are all set, we are getting a new server and decided to go with 2005 (the rest of our production machines are running 2000).
Could someone let me know if we will have any problems installing 2005 on our Development and QA Servers that are currently hosting 2000 or would it be in our best interest to purchase separate servers to run 2005? If you could share your first hand experiences that would be great.
why running the follwing qry in sql 2005 is not working?
SELECT i.namelong "AMC_FULL_NAME", s.acqdate "FORECLOSURE_ACQ_DT", m.ns_acqdate "DATE_OF_RELEASE", m.ns_conphon "SERVICER_PHONE", 0 "TOTAL_AMT_DELQ" from country i, city m, state s where m.deptno *= i.code1 and i.cd_type = 'dept' and m.uniq_id *= s.muniq_id
Can anybody point me to a resource that lists the specific discontinued 2000 mdx features? It would be great if there was a recommendation of how to accomplish the 2000 functions with 2005 syntax. We are converting 2000 AS to 2005 AS and the dimensions will not process. The error messages are useless. Thanks, Sherry
Hi guys, I’m not an expert of SQl server,I use MS SQL Server Management Studio Express to manage an Sql Server 2005. I’ve a Mdf file that I want export into backwards-compatible format that it’s possible to put inside a SQL Server 2000. How can I export my file into a compatible version for Sql Server 2000? What’s tool I need to do it? Thanks, have a nice day
