I did something stupid. I was having a problem with my application of trusted connections exceeding 15. I changed the user connections to 30 without uping the server memory configuration. Now I am out of memory and can't establish a connection with the server to up the memory configuration. I don't want to have to reinstall sql 6.5 and loose my existing data. I am on a Netfinity server with 512 megs of memory. Any suggestions? And of course our NT tape backup unit is not set up for sql backup.
Also does 30 connections and 128 megs of sql memory sound ok for a non dedicated server. About 25 users connecting to the database at any given time?
Develpers complain that Sql server is slow We running 4 databases about 400 MB each.(hotel reservations ...)
Buffer cache ( 99.8) but sometimes it goes down to (62.0) memory configuration Dynamic Do we really need more memory for 50 users or what should I check in the first place ? Thanks
We are using SQL Server 7.0. Can anyone tell me the difference between setting max connections to 150 versus setting it to 0 for unlimited. We have an application that was running slow with the 150 connections set. We changed it to 0 for unlimited and now the application flies.
Can anyone explain this? Does SQL Server do something different with these settings?
I get the following message: "Attempt to set 'tempdb' database to single user mode failed because the usage count is 3. Make sure that no other users are currently using this database and rerun CHECKPOINT."
When I do a 'sp_who active' it returns about 5 spids but they are things like Mirror Handler, Lazy Writer, Checkpoint Sleep, RA Manager, and Select. I am not able to 'kill' the spids. I get 'Only users processes are able to be killed.' How do I identifiy the 3 users that sql is saying are connected to the tempdb database? And how do I remove the 3 users?
I need to know the number of client licences that i require for a SQL Server. I want to monitor the Server for a period of a week or so to find out the max..no of user connections during that time so that i can fix the no. of user connections parameter.
i have tried using the foll Perf monitor counters : No of open user connections Client Count Max Client Count Client Limit and am still confused about the numbers. Can anyone throw some light on the difference in these counters and which one do i go by for calculating my licenses .
I am in the process of installing 7 remote desktop computers that are furnishing data to a SQL server. We will also have 40-50 Managers/Supervisors who will have access to the database for information retrieval. Are there any tools available that would allow me to monitor who is connected to the Server? My main interest in monitoring are the 7 desktops which are permanently connected to the database. Until we have some history, I would like to make certain that we can maintain a good connection between the desktops and the server
We have a production server that is configured to 100 user connections. Without any reason, the maximum connections had been exceeded and users can no longer access the sql. But if you sp_who , it displayed only 4 user connections. Since, I have an open connection before this error happens, i was able to execute sp_who. This happened 4 times since we installed the sql server. the version is 6.50.422 sp5a with hotfix.
To all gurus out there, can you give light into this problem?
Recently, my SQL Server has started getting: "Unable to connect. The maxinum of '100' configured user connections are already connected. System Administrator can configure to a higher value with sp_configure." The server has to be rebooted to recover.
What's odd is that this occurs during the weekend when only about 5-8 connections are used by various system processes. I can't tell yet what is sucking up the connections.
We use SQL 6.5 sp4 on NT4.0 sp3 for DEC Alpha. We are also using SQL Mail, Seagate Backup (with SQL drivers) and some cgis that talk to the database.
We are having a problem with the maximum number of user connections to sql. Currently we have a max of 500 connections and we are unable to connect to sql because the max number has been exceeded. The sql logs are flooded with repeated error messages about the user conncetions being maxed out.
Anyone has an idea why this could be happening? Also, can it be fixed by rebooting the server?
Newbie here.I've got my database set up in SQL 2000, and have started an Access adpfor a front end. I have 10 licenses, and at the moment the onlyaccesses are the server through Remote Desktop and one person into theADP. I started getting ODBC timeout errors when running a complexquery, so I started poking around. In the logs there's messages sayingthe maximum of 10 user connections has been reached, over and overagain. I'm not even certain that these problems are related, but itdoesn't look good.Why are all 10 connections used when there's only the server and oneclient? No one else has access to this server. And how can I stop theODBC timeout? That paticular complex query is the whole jsutificationfor using SQL over Access, so I kind of need it to work. :)Thanks in advance, maddman
I am using SQL 6.5 and I would like to know (using Isql/w) the number of users connected to my server at any given time. Thanks for your help in advance.
I get this message in the error log file (ODS17809) for sqlserver 6.5 on windows NT 4.0 Although this parameter is set to 50 which is more than enought for our environment. When I look up in current activity, I see only 4 users connected. IS there a way to find , why this message comes up and how many actula connections (alive or hanging) are with the Sql server. Well, I can increase the number of connections, but that is not the solution , as I would like to track/debug where all the connections are being used up.
I have a Sqlserver 6.5 production server used for web based applications Compaq 5500 4 GIG RAM, 4 processor
Sql Memory config on that server is 1048576 (which is 2048 MB) and the run value is 640000 (which is 1250 MB). runvalue for user connections was 500
We have only 90 user connections may increase upto 100 depends on the connections. We don't have any overload on that server.
Error: I was seeing "unable to connect maximum no. of 500 configured user connections are already connected" in the error log.
Action Taken:
I increased the user connections to 600 and rebooted the server. Immediately the same error I can see in the error log. But we have only 20 user connections at that time. I can able to connect.
I have been reading through the article pointed to by the link below on msdn and its documented that one functional limitation of user instances is "Only local connections are allowed." I didn't understand the technical details(meaning) of that limitation and hopefully some one might explain it to me so that i can understand it better.
I am working with an application unde mssql 6.5 ,sp4. We have a separate database for reporting on a different box. Each night we load a backup into the database from the production database.
I set up a stored procedure to kill all users connected to this reporting database just before the load.
THe job looks like this under scheduled tasks as a cmdexec:
Process Exit Code 1. ...[-b On error batch abort] [-O use Old ISQL behavior disables the following]<EOF> batch processingAuto console width scalingWide messagesdefault errorlevel is -1 vs 1 [-? show syntax summary (this screen)]
The killusersall is paramaterize sp that I pass the dbid of the database for whom I want all users killed. I need to put the stored procedure in the master because I egt the spid from sysprocesses.
I do not understand why the job died. Does it matter if I named the stored procedure as sp_killusersall instead of killusersall_sp which I used.
Can any one advise me about how to get the job to run? Any assistance will be greatly appreciated. Thanks you.
Is it possible to control the number of simultaneous connections one login id can have? I`d like to avoid my users to share their login ids and passwords to help them enter data into the system.
How does one enable sql connections limits for user connections per new and existing databases? how to do it on whole server per database but not set a limit per user.Looks like this must be run on each databases but what if you have 100s of databases:
USE AdventureWorks2012 ; GO EXEC sp_configure 'show advanced options', 1; GO RECONFIGURE ; GO EXEC sp_configure 'user connections', 325 ; GO RECONFIGURE; GO
What are the maximum number of user connections achievable for sql server 2000 (w/ win 2000 adv server), and how are they managed - compared with sql server 7.0 (w/ win nt 4.0)? Our group is looking at upgrading our dbase server from sql server 7.0 to sql server 2000.
Hello. I have received the follwoing error upon an attempt to Browse the Cube. All other tabs are functional, including the Calculations tab. We are running Windows Server 2003 SP2 and SQL Server 2005 SP2. Any suggestions would be greatly appreciated!
**EDIT** - Have confirmed SP1 for VS2005 is installed both locally and on server, also.
Attempted to read or write protected memory. This is often an indication that other memory is corrupt. (Microsoft Visual Studio)
------------------------------ Program Location:
at Microsoft.Office.Interop.Owc11.PivotView.get_FieldSets() at Microsoft.AnalysisServices.Controls.PivotTableFontAdjustor.TransformFonts(Font font) at Microsoft.AnalysisServices.Browse.CubeBrowser.UpdatePivotTable(Boolean translate) at Microsoft.AnalysisServices.Browse.CubeBrowser.UpdateAll(Boolean translate) at Microsoft.AnalysisServices.Browse.CubeBrowser.InitialUpdate() at Microsoft.AnalysisServices.Browse.CubeBrowser.SupportFunctionWhichCanFail(FunctionWhichCanFail function)
I've been researching AWE to determine if we should enable this for our environment.
Currently we have a quad core box with 4 gb of RAM (VMware). OS: Windows 2003 std, SQL Server 2005 std. 3GB is not set but will be as soon as we can perform maintenance on the server.
I have read mixed feedback on AWE, either it works great or grinds you to a hault. I would assume that the grinding to a hault is due to not setting the min/max values correctly or not enabling the lock page in memory setting.
We only have one instance of SQL on the server and this box won't be used for anything else aside from hosting SQL services. We do plan on running SSRS off of this server as well.
1. Will running SSRS and enabling AWE cause me problems? Will I have to reduce the max setting by the SSRS memory usage or will it share and play nice?
2. How do I go about setting the Max value? Should it be less than the physical RAM in the box? Right now its set to the default of 214748364, even if I don't enable AWE should this default value be changed?
3. It seems that even at idle the SQL server holds a lot of memory and the page file grows. If I restart the process in the morning, memory usage in taskmon is at 600mb or so. By the end of the day, its up around 2gb. How can I track down whats causing this, should this even concern me?
4. The lock Page in memory setting worries me. Everything I've read on this seems to give a warning about serious OS and other program support degradation. In some cases to the point where they have to restore the settings on the server before they can bring it back up. What are your thoughts on this.
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 have a Windows sever 2012 with sql server 2012 enterprise. Ram size is 22GB. Sometimes SQL sever takes 95% memory.My question, How to reduce memory size without killing any process because it's production server.So there are many background process is running. And,Is there any guides to learn why Memory is raise d so high and how to reduce it.
Hello, I understand that we should use SSMS -> Server Properties -> Memory to put a cap on the SQL server memory usage, therefore it gives some space memory for OS, this is based on the fact if the max memory is not specified, SQL will use whatever available memory and eventually crash the system.
My question is that when a server has SSIS and SSAS services installed along with the SQL service. Would the max memory setting covers the SSIS and SSAS memory usage, or the SSIS and SSAS has to shared the memory with OS?
