I'm very new to SQL servers. We're running SQL 6.5-SP4 and have three applications using different databases on the server (NT4-SP3).
App 1. Written in PowerBuilder using 32bit DB_LIB, NWLink IPX/SPX.
App 2. Written in VFP 5.0a using ODBC32, NWLink IPX/SPX
App 3. Written in VB using ODBC16, NWLink IPX/SPX
Something happens, which freezes all 32bit connections and prevents any other 32bit connects. Which means I can't get Enterprise Manager to connect! This does not affect the ODBC16 clients?!?!
So far the only way, I have found, to clear and fix is to get all 32bit users out of their apps and the server becomes available again. There's got to be something to prevent this, any ideas? Is there a way to trace this to find the culprit?
Declare tblCursor Cursor for select begBalance,accountDescription, accountType from account where accountType = 'Cash' or accountType = 'Accounts Receivable' or accountType = 'Inventory' or accountType = 'Other Current Asset' open tblCursor Fetch Next From tblCursor INTO @a,@b,@c While (@@Fetch_STATUS = 0) begin select @d = @d + @a end Fetch Next From tblCursor INTO @a,@b,@c
Declare tblCursor Cursor for select begBalance,accountDescription, accountType from account where accountType = 'Fixed Asset' or accountType = 'Accumulated Depreciation' open tblCursor Fetch Next From tblCursor INTO @a,@b,@c While (@@Fetch_STATUS = 0) begin select @e = @d + @a end Fetch Next From tblCursor INTO @a,@b,@c
Declare tblCursor Cursor for select begBalance,accountDescription, accountType from account where accountType = 'Other Asset' open tblCursor Fetch Next From tblCursor INTO @a,@b,@c While (@@Fetch_STATUS = 0) begin select @f = @d + @a end Fetch Next From tblCursor INTO @a,@b,@c
Declare tblCursor Cursor for select begBalance,accountDescription, accountType from account where accountType = 'Accounts Payable' or accountType = 'Other Current Liabilities' open tblCursor Fetch Next From tblCursor INTO @a,@b,@c While (@@Fetch_STATUS = 0) begin select @g = @d + @a end Fetch Next From tblCursorr INTO @a,@b,@c
Declare tblCursor Cursor for select begBalance,accountDescription, accountType from account where accountType = 'Long-Term Liabilities' open tblCursor Fetch Next From tblCursor INTO @a,@b,@c While (@@Fetch_STATUS = 0) begin select @h = @d + @a end Fetch Next From tblCursor INTO @a,@b,@c
Declare tblCursor Cursor for select begBalance,accountDescription, accountType from account where accountType = 'Equity-Retained Earnings' or accountType = 'Equity-Not Closed' or accountType = 'Equity-For Closure' or accountType = 'Income' open tblCursor Fetch Next From tblCursor INTO @a,@b,@c While (@@Fetch_STATUS = 0) begin select @i = @d + @a end Fetch Next From tblCursor INTO @a,@b,@c
Declare tblCursor Cursor for select begBalance,accountDescription, accountType from account where accountType = 'cogs' open tblCursor Fetch Next From tblCursor INTO @a,@b,@c While (@@Fetch_STATUS = 0) begin select @j = @d + @a end Fetch Next From tblCursor INTO @a,@b,@c
Declare tblCursor Cursor for select begBalance,accountDescription, accountType from account where accountType = 'expenses' open tblCursor Fetch Next From Stock_Cursor INTO @a,@b,@c While (@@Fetch_STATUS = 0) begin select @k = @d + @a end Fetch Next From tblCursor INTO @a,@b,@c
I am running NT4.0 with sp6 and SQL server 6.5 with sp3 and my system periodically freeze. The CPU shows 100% and Sql does not respond. In the NT event viewer I get a message SQLCTR60 DB-LIBRARY error - SQL Server connection timed out. How do I go about finding out what is wrong.
Is there functionality within the Table or Matrix objects to freeze columns or row headers when you scroll thru a wide or long report? Similay to the freeze panes functionality in Excel.
- Create and populate a table - Index it on a 'reference' field - Then update the table by using the index but WITHOUT updating the index (I'd like to have it available for the WHERE clause but I don't need to updtae it) - Eventually, i'd like to re-index the whole table
Hi, I saw in some websites that there are functions freeze and thaw in SQL server.I want to freeze the SQL server for some time and then use the thaw to unfreeze.I want to know how it could be done in SQL server 2005
I am attempting to open up my ssis integration project but when I try to open up packages it says @ the bottom "Validating Sequence Container" and it just stays there. I cannot click on anything and nothing is responsive. Does anyone know why this is happening?
I have a very wide report that uses a table control. I would like to "freeze" the two leftmost columns so that they remain visible when the user is scrolling horizontally (sideways). Is this possibe?
I want the header to be visible while scrolling. After changing on the static Properties FixedData=True, it is working on BIDS and Internet Explorer 11 . But is does not work in Chrome. Most of my users are using Chrome. Is there any way to fix it for google Chrome.
Our HP Proliant ML 330 G5 (3.0 Duo Core Xeon, 4 GBs RAM) server is running Windows 2003 R2 Standard 32 bit ( Win SP2) and SQL Server 2005 Standard (SQL SP2 €“ version 9.00.3054.00(Intel X86)). At random times every 1-14 days, our server will lock up. While the Windows Login screen or the standard Windows screen saver is viewable on the server still, the computer becomes completely non-responsive. The keyboard and mouse do not work and we can no longer connect to the server via a Terminal Service connection. We are able to ping the server while it is locked up though. The only way to get the server back up and running is by doing a hard power down and then power it back up.
Upon getting the server back up and running, everything goes back to working as normal with both Windows and SQL. There is nothing in any of the event logs indicating any type of issue prior to the server locking up. We are really at a loss on where to start troubleshooting this. We have no reason to think it is a hardware issue at this point but are not ruling that out. Any ideas what we can do to start tracking down the cause of this problem?
Ok... I know this is something that I've seen and probably done before....
I have a value that will show up multiple times in a table. I want to order the table by that value and then count up from 1 to however many items that it shows up as.
The example below shows the results I want. Value1 and Value2 are in the table, LineNumber is what I need to generate.
For anyone who can help me resolve this minor data issue. I am trying to clean a phone number column so that all numbers are reflected in the same way. I have phone numbers in my column in this this format:
(123)123-1234 123-123-1234 (123) 123-1234
How can I clean this column so that the numbers are reflected in this way: 1231231234
I'm having brain freez right now. Help me please!!! Thanks in Advance
I am going to test the migration of a 32bit SQL 2005 database to a SQL 2005 x64bit database server. Has anyone tried this? What can I expect? Will it work? Is there anythi I need to do?
I was just going to detach the 32bit DB, copy yhe files to the 64 bit server and reattach it.
I'm sure this has been discussed in the forums before, but I'll ask anyways. I'm replacing our GP server next year to one that will run SQL2k5 64-bit. The current server is only capable of 32bit SQL. I know with some databases changing from x64 to x32 is a bad idea...will SQL Server support it?
Windows 2003 R2 SP2 (32bit) SQL 2005 SP2 4gigs of Hot-Add RAM WSUS 3.0 SP1 SCCM 2007
I've had nothing but issues on this server until I came across the articles about using /PAE in the boot.ini to correct the 4gig RAM issues, then read that /PAE can corrupt your database.
I then enabled AWE on the SQL 2005 server using the RAM range of 1gig-4gigs.
Since this, I am seeing errors in the Application Event log on the server that states SQL is not ready to accept client connections.
So, before I go any further with this build, it this something I should be concerned about ?
Having looked at the complexities of transforming data from Oracle in a 64Bit Environment to SQL 2005, will SSIS 2008 run nativley in 64Bit. I understand that SSIS 2005 ran in 32Bit, even when in a 64Bit environment, causing great issues in accessing Oracle. Oracle released an update to compensate for this, however can someone please clarify whether SQL 2008 will have the same issues, or will SSIS 2008 be able to speak with Oracle on a 64Bit level. Regards
Hi there, Here we have got a asp.net application that was developed when database was sitting on SQL server 6.5. Now client has moved all of their databases to SQL server 2000. When the database was on 6.5 the previous development team has used oledb connections all over. As the databases have been moved to SQL server 2000 now i am in process of changing the database connection part. As part of the process i have a login authorization code. Private Function Authenticate(ByVal username As String, ByVal password As String, ByRef results As NorisSetupLib.AuthorizationResult) As Boolean Dim conn As IDbConnection = GetConnection() Try Dim cmd As IDbCommand = conn.CreateCommand() Dim sql As String = "EDSConfirmUpdate" '"EDSConfirmUpdate""PswdConfirmation" 'Dim cmd As SqlCommand = New SqlCommand("sql", conn)
cmd.CommandText = sql cmd.CommandType = CommandType.StoredProcedure NorisHelpers.DBHelpers.AddParam(cmd, "@logon", username) NorisHelpers.DBHelpers.AddParam(cmd, "@password", password) conn.Open() 'Get string for return values Dim ReturnValue As String = cmd.ExecuteScalar.ToString 'Split string into array Dim Values() As String = ReturnValue.Split(";~".ToCharArray) 'If the return code is CONTINUE, all is well. Otherwise, collect the 'reason why the result failed and let the user know If Values(0) = "CONTINUE" Then Return True Else results.Result = Values(0) 'Make sure there is a message being returned If Values.Length > 1 Then results.Message = Values(2) End If Return False End If Catch ex As Exception Throw ex Finally If (Not conn Is Nothing AndAlso conn.State = ConnectionState.Open) Then conn.Close() End If End Try End Function ''' ----------------------------------------------------------------------------- ''' <summary> ''' Getting the Connection from the config file ''' </summary> ''' <returns>A connection object</returns> ''' <remarks> ''' This is the same for all of the data classes. ''' Reads a specific connection string from the web.config file for the service, creates a connection object and returns it as an IDbConnection. ''' </remarks> ''' ----------------------------------------------------------------------------- Private Function GetConnection() As IDbConnection 'Dim conn As IDbConnection = New System.Data.OleDb.OleDbConnection Dim conn As IDbConnection = New System.Data.SqlClient.SqlConnection conn.ConnectionString = NorisHelpers.DBHelpers.GetConnectionString(NorisHelpers.DBHelpers.COMMON) Return conn End Function in the above GetConnection() method i have commented out the .net dataprovider for oledb and changed it to .net dataprovider for SQLconnection. this function works fine. But in the authenticate method above at the line Dim ReturnValue As String = cmd.ExecuteScalar.ToString
for some reason its throwing the below error. Run-time exception thrown : System.Data.SqlClient.SqlException - @password is not a parameter for procedure EDSConfirmUpdate. If i comment out the Dim conn As IDbConnection = New System.Data.SqlClient.SqlConnection and uncomment the .net oledb provider, Dim conn As IDbConnection = New System.Data.OleDb.OleDbConnection then it works fine. I also have changed the webconfig file as below. <!--<add key="Common" value='User ID=**secret**;pwd=**secret**;Data Source="ESMALLDB2K";Initial Catalog=cj_common;Auto Translate=True;Persist Security Info=False;Provider="SQLOLEDB.1";' />--> <add key="Common" value='User ID=**secret**;pwd=**secret**;Data Source="ESMALLDB2K";Initial Catalog=cj_common;' />
I m swagatika and working on a s/w company.I am facing some problem in MS SqlServer2005.
my problem is:-
My project is running on SqlServer2005 which is 32 bit support. But i want to change my project on SqlServer2005 which will be support to 64 bit . What are the steps i follow to change 32 bit to 64 bit.
This may seem like a completely foolish question, but is there any issue in using the 32bit workstation components (on XP) to connect to the 64bit server-side components? New to SQL2K5 and never had any issues using the 2K workstation/server components together.
Just curious if it's possible, and supported, to upgrade SQL 2005 from32bit to 64bit. This is on top of Windows 2003 64bit. Trying to getthe proper supported config for OM2k7 without blowing everything away.Thanks,JDP
Hi all, I've got two VLDBs on 64bit hardware platform + 64Bit-W2003K Std R2 + 64Bit SQL2005 Std Edition. If I set this guy up as the Principal, can I have the standby/member on 32Bit HW + 32Bit W2003 Std + 32Bit SQL2005?
Unfortunately, this provider seems to behave different to the one i use in 32bit :
Lets say i have a stored procedure"
create spName as
select * from mytable
when i execute the following
<%sqlstr = "exec spname"
set myRecSet = CreateObject("ADODB.Recordset")
myRecSet.open SQLStr, myConn
response.write(myRecSet(0)) %>
it gives the first value of the first row with the Connection to a 32bit SQL-Server
but myRecSet seems to be empty on my 64bit SQL Server the response.write leads to an error message.
As far as i understand this, the provider used when connecting to a 32bit Server returns the records selected by the last row of the stored procedure into the recordset, but the provider when connecting to a 64bit server does not return these results.
What can i do, if i dont want to rewrite my asp-programming. I hope somebody has the correct naming / syntax for an connection string which allows me to connect my asp-application to the 64bit SQLServer which behaves like the "old" one for 32bit.
I hope my comments are clear enough - english is obviously not my mother-tongue - and somebody can give me a hint.
I installed SQL 2005 on a 64bit server. Can I still use enterprise studio on a 32bit client machine?
The install CD's are 64bit and when I try to find the enterprise studio to install on my 32bit machine i get an error. Is there a place to download the 32bit enterprise studio? What are my options here?
There is no SQL Agent forum so if this isn't the correct place please move this post.
Windows 2003 R2 x64 with SQL Server x64.
One of the steps in a SQL job I have setup requires me to run an exe. I can run this exe from the command line or by double-clicking it on this same server but when running it from a SQL job it does not run, the job just has the status 'executing' but does not do anything. I have enabled xp_cmdshell. I have also tried calling a bat file which then runs the exe and I have tried calling the bat file with SysWOW64cmd.exe. Same problem.
It seems to me the the operating system recognises the 32bit exe and runs it in that context but the SQL Agent thread keeps trying to run it as a 64bit exe and hence never gets anywhere. (My best guess)
Is there a way to force SQL job/steps to run an exe or bat file in a 32bit thread? Any other ideas.
I wanted to make sure some things clear before setting up service broker. I have enterprise server as 64 bit and local client servers as 32 bit. I would like to know what steps do I need to take care when I am setting up service broker b/w sql server enterprise editon 2005(64 bit) and sql server express 2005 client server(32 bit)...any special considerations ...?
