Hello, i have a question that the sql server 2000 is install in window 2000 server. If i want to update to window 2003. Is that any problem in sql server 2000. I am worry about whether we will have problem after update. What i need to do? Many thanks.
View 5 RepliesI have always upgraded the OS on test servers before upgrading on production. We are in the process of upgrading hardware for a production server and are considering installing Windows Server 2003 Standard Edition vs. what previously existed on the server, Windows 2000 Standard Edition. How much of a risk would this present? I'm leaning towards not changing the OS until we have a chance to upgrade the test servers first.
Dave
Hello!I would like to change the SQL server 2000 from Standard version toDevelopment edition. I have two database running on this server, bothreplicated, with few jobs, etc ... Can you recommend the easiest way to dothis? I heard, it would be as easy as, detaching the databases, deletingcurrent SQL software, installing different one, and attaching the olddatabases back. I doubt that is true, so that's why I'm asking here for anyreal-life instructions.Thanks for your input!Kind regards,Dejan--
View 1 Replies View RelatedHi,
I am having a problem connecting my .net applications from the application server to the database server. When I run the application from my windows xp (sp2) box it works fine. When I try to connect via SQL Management Studio to the database server from the application server I get the same error.
Here is the error:
System.Data.SqlClient.SqlException: 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)
Here is the Environment:
App Server:
Windows Server 2003 Standard Edition
Inside Company's Firewall/ Network
Database Server:
Windows Server 2000 Advanced Edition
SQL Server 2000 SP4
Remote Connections to the Server is checked
Enable Protocols: Named Pipes & TCP/IP
TCP/IP Port: 1402 (I don't know why it isn't the default of 1433)
The db server is sitting out side the Company's firewall (don't ask me why). I can access it fine from inside the firewall on my XP box but not from windows server 2003. There is a web server outside the our network that also connects to the db server with no problem and that is running Windows Server 2003 Web Edition.
I can ping the db server from the app server using the IP address.
I tried using the IP address and the port 1402 in my connection string but that didn't work from any machine (XP and Server).
I imagine the issue is somehow related to the company's firewall but why would it only block Windows Server 2003 and not XP?
What do I tell the network admin to change?
Any help would be appreciated.
Thanks,
Oran
Hello y'all,
I have to do a new install of SERVER 2000 using WINDOWS 2003 . Has anyone done this. If so, what are the steps. Should I expect any problems ? Any help appreciated.
Thanx
Has anyone had trouble accessing SQL 2000 desktop install over the LAN on SBS 2003?
I cannot access my installation from the same domain, yet when I install it on a machine running something other than SBS 2003 there are no problems.
Everything seems shared correctly, and I have tried loggin on to the remote machine as Administrator with no success.
Any suggestions would be appreciated.
I have XP workstations and windows 2003 SBS. I setup an ODBC for anapplication (tried both User and System DSN), but after a few usage, I getthe following error:Connection failed:SQLState: 'HY000'SQL Server Error: 0[Microsoft][ODBC SQL Server Driver]Cannot generate SSPI context.Any ideas? Is this a bug?--Thank youPlease post only
View 3 Replies View Related
I€™m having a few issues with a server that keeps grinding to a halt and having frequent system issues requiring a reboor. It is Sql 2000 32 bit enterprise edition running 64 bit 2003 server. Im not sure of the impact of having the AWE switch set for this server because even though it has 8Gb of RAM it is only using 262Mb and is used extensively. It is set to dynamically configure sql server memory with a minuimum memory of 3075 and maximum of 6144
Is it worth me removing the AWE option or are there any more tweaks I can make to make this system run more effectively?
I don't need 2005
obulay@hotmail.com
We have a project already developed iusing VS 2003 Enterprise architect edition using sql server 2000(have lots of table and stored procs etc.)
Now planning to switch to Sql server 2005 are there any issues associated with the switch.
I mean front end programming wise asp.net and vb.net front end codes do they work straight away or need to make any changes to all the front end codes, we are using datasets, data readers calling stored procs and also using lot of hash tables and XML object to make bulk loads to sql server via sqlxml3.0 sp3.
Please help thank you very much for the information.
Hi all,I just asked some people to help me out and phone microsoft with thefollowing information, kindly they refused unless we setup a supportcontract with them first, for pre-sales information. (That really doesnot sound like good business sense to me - anyway here is our problem,if anyone could help thanks)."To tell and ask microsoft:We will be setting up a microsoft sql server 2000 instance running on awindows 2003 server.1) We need to check this can run alongside a microsoft 2003 sql server(either workgroup or standard edition), on the same machine. Are thereany .dll clashes if we do this? If there are can we run SQL Server2000, in a virtual machine running windows 2000 professional. (I have alicenced copy we can use for this).2) If we run one instance of 2000, and one of 2003 of the sql servers,can one use the processor licence model, and one use the CAL licencemodel."Thanks for any help, and any idea why they actually force you to usenews groups for pre-sales information?David
View 4 Replies View RelatedI'm trying to configure SQL server 2000 (standard edition) to send e-mail on a Small Business Server 2003. There's a great article on how to do this on a SBS 2000 server (KB304967), but it does not apply to SBS 2003. Can anyone point me to a article or white paper on how to configure SQL on a SBS 2003 server to send e-mail. Thanks.
David Neahusan
My uncle runs a small networking company and has extra licenses for Windows 2003 Server as well as SQL Server 2000. Since I just graduated from college and have started working as a database programmer (for a different company) I'd like to setup a small server at home to learn more about SQL (as well as networking, but SQL is my primary concern). I know I can setup SQL Server 2000 on my main PC, but I'd still like to set everything up in a server environment.
So, what I'm wondering is if any books (or web sites?) exist that walk you through setting up Windows 2003 Server and SQL Server 2000. I've actually set these up before (it's not very complicated) but I'm not sure if I did it the "correct" way.
Ideally if any books exist on O'Reilly's Safari Bookshelf that would be even better.
Thanks in advance,
John
We got SQL Server 2000 Standard Edition SP3 running on Windows 2003 Standard Edition server.
Now, we would like to apply windows 2003 SP2 to the Operating System.
We are concerned that whether windows 2003 SP2 is compatible with SQL server 2000 (SP3)?
I was looking at the application compatibility chart for Windows 2003 SP2.Among them Microsoft SQL Server Standard (2000) was listed but with no Service pack details. And also does Standard means standard edition there?
My Question - Is windows 2003 server SP2 compatible with SQL Server 2000 (SP3) Standard Edition? And what if I plan to apply SP4 to Sql Server ?
Please help. Thanks
Does SQL Server 2000 CE 2.0 work on Windows Mobile 2003?
Thank you,
Ken Carlino
ServiceMaster
Hello there,
We got SQL Server 2000 Standard Edition SP3 running on Windows 2003 server.
Now, we would like to apply windows 2003 SP1 to the Operating System.
We are concerned that whether windows 2003 SP1 is compatible with SQL server 2000 (SP3)?
I was looking at the application comaptibility chart for Windows 2003 SP1.Among them SQL Server 2000 Enterprise Edition Service Pack 3a was listed but not the Standard Edition.
My Question - Is windows 2003 server SP1 is compatible with SQL Server 2000 (SP3)?
Thanks
Hi,Is it possible to install on a Windows server 2003,SQL SERVER 2000 in the folowing configuration :SQL server 7.0 as a default InstanceandSQL server 2000 as a named instance.Thanks for your answer.
View 1 Replies View RelatedHi!!
I'moving my asp application to a new hosting server.
So when i tried the setup locally with the live DB & application in my test machine...
The DB access is denied when application tries to hit the DB.
DB is in seperate machine with SQL Server 2000 & application(ASP) is in Windows server 2003.....
Kindly help me with your suggestions....on what went wrong?
the first 2 parts install but the installation fails on the MSDE installation.
It gves me an error like about invalid installation media or something?
I have sql server enterprise.
plz help
I'm running the SQL 2000 upgrade wizard and this error came up in the final phases of the upgrade to SQL 2000. The phase is doing the Export Import of the Table data:
Error: Couldn't connect to the ADMIN$ share on the export machine. Verify that the MSSQLServer Service uses a NT Domain account that is part of the Administrator's group of the export machine and that both machines are in the same domain.
I've checked and service account are in the local admin group and both are in the same resource domain. The service account is in the accounts domain.
I have SQL server 6.5 with service pack 5a. Another machine with W2k and SQL server 2000 with SP3 and disables cnv6x70.dll.
Thanks
Hello,
We've some of the boxes are SQL Server 7.0 with 65 compatability and SQL Server 7.0 with 70 compatability. Now we are planing to upgrade to SQL 2000 with 80 compatability.
My question, how much complicated it is?
Is there any code changes to do in Stored Procs or Triggers or other? and what are the differences?
If lot of code changes, is there any tool to scan stored procedures?
(As we've more 5000 Stored Procedures)
If my question is not clear, let me know.
Thanks!
I have:
Server x with windows 2000 server sp4
It was SQL 2000 STD, when it was originally installed.
Now is SQL 2000 Personal edition SP4.
We dont know how it became sql 2000 personal edition.
We are assuming that an administrator had to re-install SQL and used the wrong CD.
Anybody know of any problems I can find when trying to upgrade to SQL 2000 STD??
Should I un-install and then re-install?
Hi,
I need to import an SQL string from MS Excel 2003 to SQL SERVER 2000.
The string I need to import is composed by 5 different several blocks and looks like:
Code Snippet
CommandLine01 = "USE mydb"
CommandLine02 = "SELECT Block ..."
CommandLine03 = "GO
ALTER TABLE Block...
GO"
CommandLine04 = "UPDATE Block..."
CommandLine05 = "SELECT Block..."
The detail of the SQL string is at:
http://forums.microsoft.com/msdn/showpost.aspx?postid=2093921&siteid=1&sb=0&d=1&at=7&ft=11&tf=0&pageid=1
I am trying to implement OJ's suggestion:
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2117223&SiteID=1
to use multi - batch processing to import the string to SQL SERVER, something like:
Code Snippet
Dim SqlCnt, cmd1, cmd2, cmd3
'set the properties and open a connection
cmd1="use my_db"
cmd2="create table mytb"
cmd3="insert into mytb"
SqlCnt.execute cmd1
SqlCnt.Execute cmd2
SqlCnt.Execute cmd3
Below is the code (just partial) I have, and I need help to complete it.
Thanks in advance,
Aldo.
Code Snippet
Function TestConnection()
Dim ConnectionString As New ADODB.Connection
Dim RecordSet As New ADODB.RecordSet
ConnectionString = "Driver={SQL Server};Server=myServer;Database=myDBName;Uid=UserName;Pwd=Password"
ConnectionString.Open
CmdLine01 = " USE " & myDB
CmdLine02 = " SELECT ACCOUNTS.FULLNAME FROM ACCOUNTS" ...
CmdLine03 = "GO
ALTER TABLE Block...
GO"
CmdLine04 = "UPDATE Block..."
CmdLine05 = "SELECT Block..."
RecordSet.Open CmdLine01, ConnectionString
RecordSet.Open CmdLine02, ConnectionString
ConnectionString.Execute CmdLine01
ConnectionString.Execute CmdLine02
'Retrieve Field titles
For ColNr = 1 To RecordSet.Fields.Count
ActiveSheet.Cells(1, ColNr).Value = RecordSet.Fields(ColNr - 1).Name
Next
ActiveSheet.Cells(2, 1).CopyFromRecordset RecordSet
'Close ADO objects
RecordSet.Close
ConnectionString.Close
Set RecordSet = Nothing
Set ConnectionString = Nothing
End Function
Where can I further educate myself on this subject?
Right off from the start I would assume that installing SQL Server 2000 or 2005 on Windows Server 2003 that is set up as a web server hosting a website would be against "best practices." Is my assumption right?
Common sense tells me to not to host a website on a pc that is also hosting my database.
set up windows 2003 serversql server 2000have public IP from netword soluctionsI can see websitewhat settings to i need to open up sql server to the public?
View 1 Replies View RelatedDear Sir,
I would like to use sql server 2000 as datasource with visaul web developer express.
My concern here is it compatilbe ?
Thanks
hi there,
we have sql server 2000 installed on win server 2003 and now i want to install a fresh copy of sql server 2005 on the same machine without disturbing the existing state.
is it possible or is there any chance of system/sql server malfunction
suggestions please..
..gcnivas
I need help setting up my laptop so that I can develop using Visual Studio 2003 and SQL Server 2000. I currently have both installed on my laptop but can not get them to play nicely together. Here is my connection code:
//string strConnection = "Provider=Microsoft.Jet.OleDb.4.0;";
//strConnection += @"Data Source=C:BegASPNET11ch12Northwind.mdb";
//Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=False;User ID=guest;Initial Catalog=Volkswagen;Data Source=DEREKLAPTOP;Use Procedure for Prepare=1;Auto Translate=True;Packet Size=4096;Workstation ID=DEREKLAPTOP;Use Encryption for Data=False;Tag with column collation when possible=False
string strConnection = "Provider=SQLOLEDB.1";
strConnection += @"Data Source=C:Program FilesMicrosoft SQL ServerMSSQLDataorthwnd.mdf";
////strConnection += @"Data Source=DEREKLAPTOP";
data_src.Text = strConnection;
string strSQL = "SELECT FirstName, LastName FROM Employees";
DataSet objDataSet = new DataSet();
OleDbConnection objConnection = new OleDbConnection(strConnection);
OleDbDataAdapter objAdapter = new OleDbDataAdapter(strSQL, objConnection);
objAdapter.Fill(objDataSet, "Employees");
DataView objDataView = new DataView(objDataSet.Tables["Employees"]);
dgNameList.DataSource=objDataView;
dgNameList.DataBind();
Here is the error message I get in IE:
No error information available: REGDB_E_CLASSNOTREG(0x80040154).
Description:
An unhandled exception occurred during the execution of the current web
request. Please review the stack trace for more information about the error and
where it originated in the code.
Exception Details:
System.Data.OleDb.OleDbException: No error information available:
REGDB_E_CLASSNOTREG(0x80040154).
Source Error:
Line 18: OleDbDataAdapter objAdapter = new OleDbDataAdapter(strSQL, objConnection);
Line 19:
Line 20: objAdapter.Fill(objDataSet, "Employees");
Line 21: DataView objDataView = new DataView(objDataSet.Tables["Employees"]);
Line 22: dgNameList.DataSource=objDataView;
Source
File: C:BegASPNET11ch12datagrid.aspx Line: 20
Stack
Trace:
[OleDbException (0x80040154): No error information available: REGDB_E_CLASSNOTREG(0x80040154).]
[InvalidOperationException: The 'SQLOLEDB.1Data Source=C:Program FilesMicrosoft SQL ServerMSSQLDataorthwnd.mdf' provider is not registered on the local machine.]
System.Data.OleDb.OleDbConnection.CreateProviderError(Int32 hr) +81
System.Data.OleDb.OleDbConnection.CreateProvider(OleDbConnectionString constr) +107
System.Data.OleDb.OleDbConnection.Open() +203
System.Data.Common.DbDataAdapter.QuietOpen(IDbConnection connection, ConnectionState& originalState) +44
System.Data.Common.DbDataAdapter.FillFromCommand(Object data, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior) +304
System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior) +77
System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, String srcTable) +36
ASP.datagrid_aspx.Page_Load() in C:BegASPNET11ch12datagrid.aspx:20
System.Web.Util.ArglessEventHandlerDelegateProxy.Callback(Object sender, EventArgs e) +10
System.Web.UI.Control.OnLoad(EventArgs e) +67
System.Web.UI.Control.LoadRecursive() +35
System.Web.UI.Page.ProcessRequestMain() +750
Version Information: Microsoft .NET Framework Version:1.1.4322.2032;
ASP.NET Version:1.1.4322.2032
I know that my problem is in the @DataSource part of the connection string. It works if I use the first two lines (the database file is in the same folder as the code). But not when I use it as above. I think I'm pointing to the wrong place, but I can't figure out the right place to point to. I have SQLServer running on my laptop (I think), so can anyone help me out or maybe give me some example connection strings that you have used? Thanks.
Derek
Hello,
Is there possibility to use export wizard programmatically ?
I need to copy the database structure (New db based on existing with alll constraints and relationships) ?
Thnx
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
Hi,
I run into a problem which I cannot connect to the database using SQL Server 2000 Enterprise Manager. The SQL Server 2000 was working well until I hook a SQL Server 7.0 application to it. The error message: "General OLE Error 16386, You must upgrade your SQL Enterprise Manager & SQL-DMO (SQLOLE) to SQL Server 2000 (SQLDMO) to connect to this server". I checked fixed in the sp1 for SQL Server 2000, and found no entry. In MS support website and found nothing. Need help from someone who has experience on this. Thanks in Advance.
Eugene
We're upgrading a SQL Server 2000 cluster (Active/Passive) running on Windows 2003 Server 32 - bit Standard to a SQL Server 2005 Cluster running on Windows Server 2003 64-bit Enterprise. Our existent cluster's databases are residing on SAN. We can't purchase new hardware and we have no spare hardware. We also need to move from Windows 2003 32-bit Server to Windows 2003 64-bit Enterprise Server at the same time. We want to keep downtime to a bare minimum.
What we were thinking was the following steps... Anyone try this?
1. Break the link between the servers. Or should we just evict the passive node?
2. Install a fresh copy of windows 2003 64-bit server on one side along with SQL Server 2005. While this step is running, the active node would still be live on Windows 2003 32-bit Server and SQL Server 2000 serving our customers.
3. Bring the active server down.
4. Create new cluster on the newly upgraded server and assign the same cluster name and IP as the original one.
5 Bring the luns from SAN to the newly upgraded server and initialize SQL Upgrade
6. As a final step, the old active node will be rebuilt, we would install a fresh copy of windows 2003 64 - bit server on it and sql server 2005. At this point we would bring it back into the cluster and the cluster would be complete again.
Thoughts?
Hi
I would like to get some advise on the capacity of concurrent users on Access 2000. Here is my situation:
- I have a vb6 application that connects to one database(currently is a access 2000 mdb) via Adodc .
- There will be 6-8 copies of this application running on different PCs and that database is shared .
- All 6 PCs read/write to that database concurrently.
I wonder would Access 2000 be a reliable choice?
Thanks for your time