How To Resolve An Indefinite Wait State On Update Command In SQL2005 (64bit 2003 Server)?
Jun 16, 2006
I am in the process of moving a SQL2000 database to a SQL2005 database.
Porting from: SQL200, Windows Server 2000(SP4) (32 bit dual processor)
to:SQL2005, Windows Server 2003(SP1) (x64 bit dual processor)
After porting the database from SQL2000 to SQL2005 (no changes) running the same update statement from Management Studio on the 2003 Server and and Query analiser on the 2000 Server.
SQL2000 completes the command in 2 minutes SQL2005 is still running after 60 minutes.
SQL2000 is the live/production system with users connected, the SQL2005 is in a test environment with no other processors running.
When the problem first showed up the SQL2005 activity monitor displayed CXPACKET wait type on 2 processes with the same pid number. I now no longer have any wait type being displayed but my wait time is increasing rapidly. No block is reported.
I assume that I have an CXPACKET lock problem.
Am I correct that I have a CXPACKET problem and if so what is the resolution?
The update statement is as follows...
update BI_LENDING_TRANSACTIONS
set [Balance Movement Month] = M.[Balance Movement Month]
from BI_LENDING_TRANSACTIONS as T,
BI_BALANCE_MOVEMENT_DATES as M,
BI_COMPANIES as C
where (T.[Transaction Date] >=
(SELECT DATEADD(d, - 70, minDate) from (select min([Transaction Date]) minDate
from p_BI_LENDING_TRANSACTIONS) t1)
OR
T.[Transaction Date] >= C.[MostRecentSnapShotDate] or
T.[Value Date] = T.[Balance Movement Month] ) and
T.[Value Date] <= C.[MostRecentSnapShotDate] and
T.[Value Date] >= T.[Transaction Date] and
T.[Company_Code] = M.[Company_Code] and
T.[Value Date] > M.[SnapShotFromDate] and
T.[Value Date] <= M.[SnapShotToDate] and
C.[Company_Code] = M.[Company_Code]
I get this problem when tryoing to connect to the surface area configuration for services & connections As well as for features. However I can connect via another computer and change the options accordingly but I just can't do it locally from the server ? Does any one know why please, the links in the message don't help ?
=================================== An exception occurred in SMO while trying to manage a service. (Microsoft.SqlServer.Smo) ------------------------------ For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.3042.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.InnerWmiException&LinkId=20476 ------------------------------ Program Location: at Microsoft.SqlServer.Management.Smo.Wmi.WMIProxy.ExecProcess(Object request) at Microsoft.SqlServer.Management.Smo.Wmi.WMIProxy.ProcessRequest(Request req) at Microsoft.SqlServer.Management.Smo.Wmi.WmiSmoObject.EnumChildren(String childTypeName, WmiCollectionBase coll) at Microsoft.SqlServer.Management.Smo.Wmi.ServiceCollection.InitializeChildCollection() at Microsoft.SqlServer.Management.Smo.Wmi.ServiceCollection.get_Count() at Microsoft.SqlSac.MainPanel.FormFeatures..ctor(String machineName, Form callingForm) =================================== Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum) ------------------------------ For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&LinkId=20476 ------------------------------ Program Location: at Microsoft.SqlServer.Management.Smo.Enumerator.Process(Object connectionInfo, Request request) at Microsoft.SqlServer.Management.Smo.Wmi.WMIProxy.ExecProcess(Object request) =================================== ------------------------------ Program Location: at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo) at System.Management.ManagementObjectCollection.ManagementObjectEnumerator.MoveNext() at Microsoft.SqlServer.Management.Smo.Wmi.WmiBase.BuildDataTable(ManagementObjectCollection listManagementObject) at Microsoft.SqlServer.Management.Smo.Wmi.WmiBase.BuildResult(ManagementObjectCollection listManagementObject) at Microsoft.SqlServer.Management.Smo.Wmi.WmiBase.GetData(EnumResult erParent) at Microsoft.SqlServer.Management.Smo.Environment.GetData() at Microsoft.SqlServer.Management.Smo.Environment.GetData(Request req, Object ci) at Microsoft.SqlServer.Management.Smo.Enumerator.GetData(Object connectionInfo, Request request) at Microsoft.SqlServer.Management.Smo.Enumerator.Process(Object connectionInfo, Request request)
I am in the process of moving a SQL2000 database to a SQL2005 database.
Porting from: SQL200, Windows Server 2000(SP4) (32 bit dual processor 4GB RAM) to:SQL2005, Windows Server 2003(SP1) (x64 bit dual processor 4GB RAM)
After porting the database from SQL2000 to SQL2005 (no changes) I then compare an update statement running from Management Studio on the 2003 Server and and Query analiser on the 2000
Server.
SQL2000 completes the command in 2 minutes SQL2005 is still running after 60 minutes.
SQL2000 is the live/production system with users connected, the SQL2005 is in a test environment with no other processors
running.
The SQL2005 activity monitor shows: ----------------------------------- 3 suspended processes in CXPACKET wait state and 2 runnable process high CPU counts (SQLServer running at 100% cpu). All processes with the same Process ID. Wait time is 0 High CPU counts for the runnable processes. Low physical IO No lock conflicts
When I add the "option (maxdop 1)" to the update statment then:
The activity monitor shows: --------------------------- 1 runnable process with a high CPU count (SQLServer running at 50% cpu). Wait time is 0 High CPU count for the runnable processe. Low physical IO No lock conflicts
How do I debug this situation? Why is the SQL2005 unable to complete the task?
The update statement is as follows... -------------------------------------
update BI_LENDING_TRANSACTIONS set [Balance Movement Month] = M.[Balance Movement Month] from BI_LENDING_TRANSACTIONS as T, BI_BALANCE_MOVEMENT_DATES as M, BI_COMPANIES as C where (T.[Transaction Date] >= (SELECT DATEADD(d, - 70, minDate) from (select min([Transaction Date]) minDate from p_BI_LENDING_TRANSACTIONS) t1) OR T.[Transaction Date] >= C.[MostRecentSnapShotDate] or T.[Value Date] = T.[Balance Movement Month] ) and T.[Value Date] <= C.[MostRecentSnapShotDate] and T.[Value Date] >= T.[Transaction Date] and T.[Company_Code] = M.[Company_Code] and T.[Value Date] > M.[SnapShotFromDate] and T.[Value Date] <= M.[SnapShotToDate] and C.[Company_Code] = M.[Company_Code]
We've got a Windows 2003 (64 bit edition) box to use as our Database server.
I installed SQL Server 2005 (Standard Edition) on the machine, but I have a feeling it has installed the 32 bit version and not the 64 bit version.
The reason I think this is that the MSSQL directory is under the 32 bit program files directory and not the 64 bit directory, and also when I look at the service properties it says it's running from WOW6432 registry entry.
Is there a separate disc for the 64bit version? Does the installer automatically work out which version to install or is there some sort of switch I have to do to tell it to install the 64 bit version.
Now I'm trying to run PHP web application on x64 2003 Server with Microsoft SQL Server 2005. The version of PHP is 5.2.3. and the web application should be run as 64bit applications. Since there seems no way to use php_mssql.dll on the environment, I'm trying to use SQL Server 2005 Driver for PHP but when PHP loads php_sqlsrv.dll, an error has occurd and there's a following message in an error log...
PHP Warning: PHP Startup: Unable to load dynamic library 'c:phpextphp_sqlsrv.dll' - %1 is not a valid Win32 application
From this message, I thought the distributed libraries for Windows would be for a Win32 environment but there seemed no information that says the libraries run on Win32 environment only.
We are having major performance issues with Microsoft SQL 2005 64bit Standard Editions performance on Windows Server 2003. We have an SSIS package running very slowly (and other sql tasks) on our two quad core cpu system with 8gb of ram and running a 500gb mirrored SCSI (Raid 1) drive system. The database running on the server is about 11gb.
Does anybody have any suggestion we could try to increase the performance of the server? I've run a defrag several times which helps a little but I was hoping I could do something else to increase the performance.
I'm experiencing a very annoying failure when trying to do a backup - I hope you can help where others (including me) have failed.
The setup is a SharePoint Portal Server 2003 version 11.0.8126.0 running on Windows server 2003 Standard edition Service pack 1; it has a SQL-server 2005 version 9.0.2047 running on Windows server 2003 Standard edition Service pack as a back-end.
When I issue a backup of the SharePoint database XXX_SITE which holds round 4 gb. of data (mainly documents) the backup process hangs with a Wait Type 'MSSEARCH', it makes no difference whether I issue it as a single job, or through a maintenance plan.
I tried to stop the MsSearch service on the SharePoint-server, and disabled the Full-Text search on the database but it makes no difference.
The only way I can get a backup is to reboot the server on which SQL-server resides (restarting the SQL-server makes it rather unstable), and do a manual back-up shortly after.
Recently we observed a problem. We are running stored procedure through our c# code. Three machines access the server and update or insert in the required tables in the server. If there is no data in the server, on installing first time our application usually our database is clean. then stored procedure works fine, it takes around 10 to 15 sec to execute. Next time if execute the time goes up to minutes like 15 mins. Next time it goes for hours around 4 hrs. Even to update 4 or 5 records it takes time. Initially we thought it was because of the size of the data and we tried to re tune on indexes, it did not solve. But now what we observe is even with less number of records in server also it wouldn't come of the execution for hours. Now are executing the just the SP in the SQL manager studio to see the time. That one also is executing for hours. when looked at the activity monitor the process goes to suspend state with wait type ASYNC_NETWORK_IO.
When we comment one of the query is working fine. Is this something to do with the query I am not sure. If that is the case it should not work every time.
The query makes any sence or is there any way to write it in better way
'UPDATE [server].[dbo].[DocumentMetadata] SET DocumentInfoID = b.DocumentInfoID, [Name] = b.[Name], MetadataType = b.MetadataType, [Value] = b.[Value], ValueType = b.ValueType FROM [server].[dbo].[DocumentMetadata] a WITH (UPDLOCK) INNER JOIN (SELECT c.DocumentInfoID, c.[Name], c.MetadataType, c.[Value], c.ValueType FROM MACHINENAME.[Client].[dbo].[DocumentMetadata] c INNER JOIN MACHINENAME.[Client].dbo.DocumentInfo DINF ON c.DocumentInfoID = DINF.DocumentInfoID INNER JOIN MACHINENAME.[Client].dbo.Path d on DINF.NativeFileID = d.PathID INNER JOIN MACHINENAME.[Client].dbo.ActiveDataSource ADS ON d.DataSourceID = ADS.DataSourceID WHERE ADS.ProjectID = ''' + @ProjID + ''') b ON a.DocumentInfoID = b.DocumentInfoID AND a.[Name] = b.[Name]'
'INSERT INTO [server].[dbo].[DocumentMetadata] (DocumentInfoID, [Name], MetadataType, [Value], ValueType) SELECT c.DocumentInfoID, c.[Name], c.MetadataType, c.[Value], c.ValueType FROM MACHINENAME.[Client].[dbo].[DocumentMetadata] c INNER JOIN MACHINENAME.[Client].dbo.DocumentInfo DINF ON c.DocumentInfoID = DINF.DocumentInfoID INNER JOIN MACHINENAME.[Client].dbo.Path d on DINF.NativeFileID = d.PathID INNER JOIN MYCLI.[Client].dbo.ActiveDataSource ADS ON d.DataSourceID = ADS.DataSourceID WHERE ADS.ProjectID = ''' + @ProjID + ''' AND Ltrim(rtrim(c.DocumentInfoID))+ ltrim(rtrim(c.[Name])) NOT IN (SELECT Ltrim(rtrim(DocumentInfoID))+ ltrim(rtrim([Name])) FROM [server].[dbo].[DocumentMetadata])'
We have been fighting it out for so many days. Can anybody help
I have an SQL2005 db residing on a 64bit server.I can load and run my App, provided it is installed on the server.However when I try to run from a Client's PC I get timeout errors.
Initially the error was Remote connections not allowed,but I have overcome this by ensuring SQLbrowser was running and that AllClient and Server Prodtocols were enabled.
I now keep getting a message the timeout has expired.
I devloped this app with vs2005 and SQL 2005 express, everything seems to work fine, when I deploied the app to my web server I got a few different error messages that I worked through but now stuck on this one. i am sure it is something with SQL 2005 server. is there anywhere that has a good check list for doing things right in asp and SQL deployment? here is the error message i am getting from debugging. The SELECT permission was denied on the object 'Categories', database 'Blog', schema 'dbo'. 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.SqlClient.SqlException: The SELECT permission was denied on the object 'Categories', database 'Blog', schema 'dbo'. Source Error: Line 33: SqlConnection connection = CreateConnection();Line 34: SqlCommand command = CreateCommand(connection, query, parameters);Line 35: SqlDataReader reader = command.ExecuteReader(CommandBehavior.CloseConnection);Line 36: Line 37: Type datatype = factory.GetDataType(); Source File: c:InetpublogplankroadApp_CodeUtilitiesSqlDatabase.cs Line: 35
Have Server2003 Enterprise running IIS6 and sql2005. Lease is up and have to migrate to new server. Any migration tools out there to make this easier? Saw one for exchange, 2000-2003, but not one to do the server2003-server2003 and/or IISy-IIS6 and SQL2005-SQL2005. Any pointers for assistance?
So, I'm fairly new to SQL, and I'm working with a SQL2k5 Database with pre-made packages and what-not. This database was setup before I started this job, and now I'm trying to improve part of the processing in SQL, and so far so good, but I can't figure a couple things out.
The main problem is when I start a SQL command to launch a DTS package from a .sql file, how can I make it wait for the package to complete or fail before moving onto the next part of the .sql script? Hope it's a simple question, I've just taught myself enough SQL to get by in a couple of weeks.
I'm running SQL Server 2005 SP2 64bit under Windows Server 2003 64 bit The system is the replication distributor as well. Transactional replication.
But I can't create the snapshot!
I have run snapshot.exe repeteadly with all parameters in a command prompt and it crashes at various BCP percentages. The error is like this: 2007-10-16 00:38:56.32 [10%] Bulk copied snapshot data for article 'Dictionary (part 14 of 20)' (1656 rows). 2007-10-16 00:38:56.32 [10%] The replication agent had encountered an exception. 2007-10-16 00:38:56.32 Source: Replication 2007-10-16 00:38:56.32 Exception Type: Microsoft.SqlServer.Replication.NativeSqlConnectionException 2007-10-16 00:38:56.32 Exception Message: Data conversion failed 2007-10-16 00:38:56.32 Message Code: 02007-10-16 00:38:56.32 2007-10-16 00:38:56.32 Call Stack: 2007-10-16 00:38:56.32 Microsoft.SqlServer.Replication.NativeSqlConnectionException: Data conversion failed 2007-10-16 00:38:56.32 at Microsoft.SqlServer.Replication.Snapshot.SqlServer.NativeBcpOutProvider.ThrowNativeBcpOutException(CConnection* pNativeConnectionWrapper) 2007-10-16 00:38:56.32 at Microsoft.SqlServer.Replication.Snapshot.SqlServer.NativeBcpOutProvider.BcpOut(String strBcpObjectName, String strBcpObjectOwner, String strBaseBcpObjectName, Boolean fUnicodeConversion, String strDataFile, String strLoadOrderingHint, String strWhereClause) 2007-10-16 00:38:56.32 at Microsoft.SqlServer.Replication.Snapshot.SqlServer.BcpOutThreadProvider.DoWork(WorkItem workItem) 2007-10-16 00:38:56.32 at Microsoft.SqlServer.Replication.WorkerThread.NonExceptionBasedAgentThreadProc() 2007-10-16 00:38:56.32 at Microsoft.SqlServer.Replication.MainWorkerThread.AgentThreadProc() 2007-10-16 00:38:56.32 at Microsoft.SqlServer.Replication.AgentCore.BaseAgentThread.AgentThreadProcWrapper() 2007-10-16 00:38:56.33 [10%] Bulk copied snapshot data for article 'Dictionary (part 15 of 20)' (1487 rows). 2007-10-16 00:38:56.33 [10%] Bulk copying snapshot data for article 'Dictionary (part 20 of 20)'
the fact that BCP continues to copy data after the error makes me believe the crash occurs somewhere else.
How can I isolate the offending table? Can I capture the BCP commands issued?
I have installed windows 2003 R2 64bit on one of the system, but my devlopment team pointed out that there is no odbc driver available.
I check it for odbc driver on OS cd but i do not found any relevant files/packages, can any one tell me from where I can download the ODBC driver for windows 2003 64bit OS.
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 an application written in VB6 that creates a ADO connection using the (native SQL2005 clien)t from the client to SQLServer 2005 on Server 2003 configured as a stand alone server. The application works great on XP and has for a number of years.
Now I am attempting to deploy in Vista and using the same code the connection speed CRAWLS. it's in the magnitude of atleast 10 times slower. It eventualy works but the selects and doing a readnext against the resulting record set is at a snails pace.
What am I missing. It's has to be some sort of configuration problem somewhere.
I've been having no luck trying to install SQL 2k 32bit on Windows 2003 64bit x86 SP1 - I've found several articles regarding needing to put SP4 on the 64bit OS, but my problem is the SQL 2k 32bit ",,x86setupsetupsql" won't run.
I consistantly receive a "...(localuserdir)Local.ins. Unable to load installaion instructions. Error 703."
And of course, the SP4 setup won't run because there is not an existing SQL Service to upgrade.
When I run the parse command in SSMS, it merely does a syntax check. When I run through the export data wizard by right clicking on a table, it allows a query as the data source. When I click on the parse button in the window that accepts that query, it resolves object names and notifies me of invalid ones. I'd really like the same thing to happen when I parse in SSMS...
We have a 64bit installation of SQL Server (SSIS, SSAS) running and working fine. There is a requirement to install 64bit SSRS on this existing setup. The problem is: While running the SQL Server Setup wizard, the Reporting Services checkbox remains greyed out. In other words, there isnt an option to select SSRS for installation. So the question is: Is it even possible to install 64bit SSRS on an existing 64bit SQL server installation - given that SSRS wasnt installed during the first pass. PS: The SQL Server is SP2 on a Windows Server 2003 configured as an App Server.
During our DR drill we found that the same code which used to run perfectly fine on our Primary Data Centre is running very slow on Disaster Recovery DB Server and there are Lot's of open transaction with sleeping status and waittype as 'AWAITING COMMAND'.CPU, Memory and disk utilization are good. The ping reply between the app server and the DB server is well within the limit's even blocking is not their, also nothing is reported in the error logs. We are using SQL server 2014 STD 64 BIT on Windows Server 2012.
I'm trying to run a test from my test environment which is a non-domain Windows 2000 server to access my domain 2003 with SQL2005. I have install 2005 tools to try to access the SQL server.
- I have try following the KB265808 - no success. - Reading alot of blogs and it seems all are pointing to the same problem. "Remote access" but the settign is enabled.Error Message:
TITLE: Connect to Server ------------------------------
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)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=53&LinkId=20476
Question: Could Windows 2003 security be blocking access? I'm using sa account to access.
Also, sa account does not seems to work for remote access. It is ok when accessing locally.
Just installed a new version of SQL2005 on a brand new Application Server.
However, when i fired up Access 2003, it gives me some chaos about how Access isn't compatible with SQL2005. Fantastic lack of backward compatibility straight out the box.
Ok, so I do as it says and download all the updates.
Try again... Still won't allow me.
Wen't to Control Panel > Data Sources and confirmed the Native Client is in there. Added a System DSN for the new Server.
Tried Access again, still not working?? What the...
Why can't I create a new project in Access 2003, and edit it from my desktop instead of sitting on the server for every table modification? I hate designing tables on the SQL studio.
Any clues or help would be great. I'm just disappointed at the moment, on how this is holding up my database projects.
I have many problem when I try to install SQL 2005 Ets edition ia64 on a 2003 ets Itanium edition.
When I launch the setup, all is all right. But during the installation, it tryes to start MSSQL services.
The staring of this service failed. So I try to start the service mannually. Nothing.
Error messages I can get (in the event log) :
Source : Service Control Manager ; ID : 7000
Description :Service SQL Server (MSSQLSERVER) failed to start due to the following error: The service did not respond to the start or control request in a timely fashion.
Source : MsiInstaller ; ID 10005
Description : Product: Microsoft SQL Server 2005 (64 bits) -- Error 29503. Failure of the starting of service SQL Server. For more information, to see the headings of on line help €œProcedure: to post the files newspapers of installation of SQL Server 2005€? and €œmanual Starting of SQL Server€?. This error is (1053) The service did not respond to the start or control request in a timely fashion.
I have a database table which needs to make the Index "ParentREF, UniqueName" unique - but this fails because duplicate keys are found. Thus I now need to cleanup these duplicate rows - but I cannot just delete the duplicates, because they might have rows in detail tables. This means that all duplicate rows needs an update on the "UniqueName" value - but not the first (valid) one!
I can find those rows by
SELECT OID, UniqueName, ParentREF, CreatedUTC, ModifiedUTC FROM dbo.CmsContent AS table0 WHERE EXISTS ( SELECT OID, UniqueName, ParentREF FROM dbo.CmsContent AS table1 WHERE table0.ParentREF = table1.ParentREF AND table0.UniqueName = table1.UniqueName AND table0.OID != table1.OID ) ORDER BY ParentREF, UniqueName, ModifiedUTC desc
...but I struggle to make the required SQL (SP?) to update the "invalid" rows. Note: the "valid" row is the one with the newest ModifiedUTC value - this row must kept unchanged!
ATM the preferred (cause easiest) way is to rename the invalid rows with UniqueName = OID because if I use any other name I risk to create another double entry.
Will it be possible to do an in-place upgrade from SQL 2000 Server Enterprise SP4 32 bit running on top of 64 bit Windows 2003 Enterprise , clustered, to SQL 2005 Enterprise 64 bit? The 32 bit SQL 2000 to 64 bit SQL 2005 in place upgrade seems questionable to me... Anybody tried anything like this?
i am using visual web developer 2005 and SQL 2005 with VB as the code behindi am using INSERT command like this Dim test As New SqlDataSource() test.ConnectionString = ConfigurationManager.ConnectionStrings("DatabaseConnectionString1").ToString() test.InsertCommandType = SqlDataSourceCommandType.Text test.InsertCommand = "INSERT INTO try (roll,name, age, email) VALUES (@roll,@name, @age, @email) " test.InsertParameters.Add("roll", TextBox1.Text) test.InsertParameters.Add("name", TextBox2.Text) test.InsertParameters.Add("age", TextBox3.Text) test.InsertParameters.Add("email", TextBox4.Text) test.Insert() i am using UPDATE command like this Dim test As New SqlDataSource() test.ConnectionString = ConfigurationManager.ConnectionStrings("DatabaseConnectionString").ToString() test.UpdateCommandType = SqlDataSourceCommandType.Text test.UpdateCommand = "UPDATE try SET name = '" + myname + "' , age = '" + myage + "' , email = '" + myemail + "' WHERE roll 123 " test.Update()but i have to use the SELECT command like this which is completely different from INSERT and UPDATE commands Dim tblData As New Data.DataTable() Dim conn As New Data.SqlClient.SqlConnection("Data Source=.SQLEXPRESS;AttachDbFilename=|DataDirectory|Database.mdf;Integrated Security=True;User Instance=True") Dim Command As New Data.SqlClient.SqlCommand("SELECT * FROM try WHERE age = '100' ", conn) Dim da As New Data.SqlClient.SqlDataAdapter(Command) da.Fill(tblData) conn.Close() TextBox4.Text = tblData.Rows(1).Item("name").ToString() TextBox5.Text = tblData.Rows(1).Item("age").ToString() TextBox6.Text = tblData.Rows(1).Item("email").ToString() for INSERT and UPDATE commands defining the command,commandtype and connectionstring is samebut for the SELECT command it is completely different. why ?can i define the command,commandtype and connectionstring for SELECT command similar to INSERT and UPDATE ?if its possible how to do ?please help me
I found sql2005 Enterprise cannot be installed under Simplied Chinese win 2003, the only thing i suspect is that win2003 is an envaluation copy with netframework 2.0 be installed.
I just installed the 64bit Vista and than wanted to install the 64bit SQL 2005 Std. Server on it.
Note: I downloaded my license from https://licensing.microsoft.com/eLicense/L1033/ProductDetail.Asp?SKU=228-05338.
Installing from SQLSTDSEL.ISO file results in the warning that for the REPORT- Server the .NET version has to be 32bit.
Stopping the installation at this point and try to install from SW CD SQL Svr Standard Edtn 2005 64Bit X64 English #1 x64 MLF.x11-57664 + SW CD SQL Svr Standard Edtn 2005 64Bit X64 English #2 x64 MLF.x11-57665 does not give the above error but on the other hand installs no server at all since somehow the installation routine is not working at all.
Installing now - after at least analysis server and reports server are 64bit and installed - from the first mentioned ISO results in the installation of the DB- Server.... but as a 32bit installation.
Now I wonder what did not work out - so maybe someone here has an idea if and how this problem is solveable.
I'm trying to update a table in MyDB1 with a value in MyDB2 on the same SQL server (2000)
UPDATE MyDB1.dbo.Users SET MyDB1.dbo.Users.InstantASP_UserID = MyDB2.dbo.InstantASP_Users.UserID FROM MyDB2 INNER JOIN dbo.aspnet_Membership a ON a.UserId = MyDB1.dbo.Users.UserID WHERE MyDB2.dbo.InstantASP_Users.EmailAddress = a.Email
I don't want to have to create a linked server. It's on the same box.