I may not be the best forum for this post, however I believe some one
can still help me or direct me somewhere else.
I'm finding that win 2003 x64 and SQL 2005 CTP is slower than win 2003
and SQL 2000.
Machine A: Opteron 2.2 (248) w/ 2 cpus. 8GB memory. SCSI disk array.
Windows Enterprise 2003 x64 final release. SQL Server 2005 enterprise
CTP.
Machine B: Opeteron 2.2 (248) w/ 2 CPUs. 4GB Memory. IDE Drives.
Windows Server 2003 (32bit) and SQL Server 2005 (standard).
I'm using Cognos' DecisionStream as the ETL tool (32bit). I have the
identical job on both machines. Machine A is slower to do my nightly
build (1h 20m) vs. Machine B (50m).
I've done no tweaking of the databases. I Used SQL 2005's studio to
copy the database from Machine B to Machine A.
The only major difference is the O/S and SQL, the machines are same
speed, however Machine A has twice the memory and faster disk; so I
would expect it to be faster.
Can anyone think of smoking guns I might be missing?
TIA
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:
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"
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
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
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.
When windows 2003 server is not log on to the domain, SQL worksfine.(workgroup) Everyone can connect to SQL. When everyone is on thedomain, nothing can connect remotely to SQL.
I'm working on deploying an ASP.NET 2.0 app onto a Windows 2003 server and I'm having trouble with SQL 2000 authentication. When I run my app from my development box running IIS 5.1 I have no problems. In order to get it to work on my this machine, I had set the account for anonymous access to run under an ASPNETDOMAIN account and configured my SQL database to allow this account.On the Windows 2003 box with IIS 6.0, I've done the same thing with anonymous access for the web app, and also created an application pool that the app runs under and have set the application pool to run under the same account. It appears the app is looking for a local SQL 2005 instance (which doesn't exist). Why would it do this and what do I need to change for this to work?Error: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: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)Stack Trace:[SqlException (0x80131904): 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: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)] System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) +735043 System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) +188 System.Data.SqlClient.TdsParser.Connect(Boolean& useFailoverPartner, Boolean& failoverDemandDone, String host, String failoverPartner, String protocol, SqlInternalConnectionTds connHandler, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, SqlConnection owningObject, Boolean aliasLookup) +820 System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance) +628 System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance) +170 System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection) +130 System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup) +27 System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) +47 System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) +105 System.Data.SqlClient.SqlConnection.Open() +111 System.Web.Management.SqlServices.GetSqlConnection(String server, String user, String password, Boolean trusted, String connectionString) +68
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
I need to max out on RAM somewhere around 3 to 4 GB and I am using SQL 2000. Standard SQL 2000 RAM is limited to 2 GB. SQL Enterprise 2000 is maxed out around 32GB and it cost is $1K. I need to purchase a Windows based SQL package but I can't find the specs on SQL Standard 2003 (which is ~$700) to compare. What is the Max RAM for SQL Standard 2003? Which is a better purchase relative to RAM? What O/S is recommended as this also limits RAM usage?
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
I installed MS SQL 2000 on a Windows 2003 server cluster (no servicepacks). Both nodes are online and both domain controllers are online.I tried to install SP3 and got the following error:--------------Logon Account could not be validated.No authority could be contacted for authentication.---------------I installed SQL SP 2 and did not get the error but I do get it everytime I try to install SP3.Does anybody have an idea that might help resolve the problem.
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 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.
Hi !when installing sqlserver 2000 on a Windows 2003 server it explicitlytells "server not compatible with Windows 2003" during install, but itcan carry on.After we applied serfice pack 3a then the db server seems to runnormally, but does it risk to behave randomly afterwards ???Is sqlserver 2000 standard edition compatible with Windows 2003 server?Or does it exist a specific sqlserver edition for Win2003 ?thanks !Patrice
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)?
Can SQL 2000 32 bit run on a Windows 2003 64-bit Intel OS installation? What about the SQL 2000 64 bit version? Is the Enterprise Edition required for this?
I have been running Windows 2003 64bit and SQL2000 SP4 for over 2 months with out any issues.
Sadly we had a server crash "NTldr missing or corrupted"
now when the one engineer looked at it he suggested to reload the server with Windows 2003 32 bit version as there were known compatibility problems between 2003 64bit and SQL 2000 32bit but that you can install SQL 2000 32bit onto a Windows 2003 64 bit server.
Now i dont really believe this statement nor can i find any documentation supporting this. I believe this server might have crashed due to a new patch that was released the last 2 or 3 week either on Windows or SQL. Does anyone know where i can verify what patches was released?
Maybe someone else can share their thoughts with me.
I have used the Access 2003 Upsize Wizard to create SQLServer Tables, all worked fine except I cannot Update the tables from Access.
The idea being to use Access Forms as the front end to an SQLserver back end as the Access database is quite complex and filled with macros and queries, not one of mine.
I can update the table in SQLServer but the connected tables at the Access end are read only. Why?
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).]
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.
I Created one database named login.sdf in sql Ce ,i created one table login having two fields (username and password).it is working well.I trying to synchronise these with SQL2000 using Active sync.it is not working ..And one more things ,i tried to connect the default pocket PC 2002 emulator with Active sync.it is also not working.can anybody give some solution for these problem
I want to view the sample databases within Access 2003. When I try to view them an error message appears saying I need MSDE 2000 but this will not run on Windows Vista which is my operating system. What do I need to view the sample database as well as develop applications within Access using SQL server?
How to Connect sqlServer 2000 in Pocket PC 2003 Application. In Packet PC 2003 Application I have to connect to sql server 2000 on my machine. The application gives error if connected using sqlConnection. Is SQL server CE necessary to connect to sql server 2000 in .Net Compact Framework?
After differential restore I start Remedy service. It starts in few seconds.
After full restore the same service takes 15 minutes to start. Bothe the things are done through SQL service agent. Even manual restaring the service also takes 15 minutes after full restore. WHy is it happening this way?
I am looking for some recommendations for memory sizing and options for a SQL 2000 Cluster. This is a two node cluster built on Windows 2003 ENT SP1 (x86). Both the nodes have the following hardware:
- 4 x Dual Core AMD Processors - 16 GB Memory - EMC Shared Disk
We are running six SQL 2000 instances and don't expect each of these instances to use more than 1.7 GB of memory. All these instances are going to support BizTalk 2004 Databases. I already have /PAE enabled on the nodes. I am looking for the following answers:
- Do I need to enable AWE on all the instances even if the instances ? Currently, we don't have that enabled and we have seen some issues regarding excessive paging even when there is physical memory available. The DBAs think that we don't need to enable AWE. I am bit confused on this one.
- We normally run 3 instances on each node and would like size the cluster in such a way that it can take six instances in case of a node failure
I have a Windows 2003 Enterprise x64 edition cluster setup and functioning normally. Now, I am trying to get SQL Server 2000 installed as a failover cluster but am having some difficulty. When installing, I get the message '[sqsrvres] ODBC sqldriverconnect failed' in the event log. The message happens when the installer is trying to bring the SQL Server Service resource online.
I am able to ping the name of the instance successfully. I am able to manually start the 'MSSQL$InstanceName' service. I have turned off the firewall on both machines, but this did not help. I have the DTC Service setup as a resource in the same cluster group.
I also read http://support.microsoft.com/default.aspx?scid=kb;en-us;815431 which seemed promising, but did not reolve the problem.
