I need to know the maximum number of concurrent connections to SQL Server 2008
Why would your database need to handle that many connections?
At any rate if you have a windows server which is going to run an application (regardless of the applications running) that needs to handle a lot of connections then the server itself must be configured for that.
n the design, data will be accessed by medical institutions so I have to consider connections to the server in advance.
That is a business requirement not an implementation requirement. So exactly what do you think is going to be connecting to your database?
And did you actually attempt to size this? How many requests will your product generate? How long will it take to process them? How many users will be using it? What is the expected sustained rate? What is the burst rate?
If a request took 1 second and was made once an hour then you could handle 10,800,000 requests without reconfiguring anything on the database server.
There are less than 6,000 hospitals in the US. There are less than 200,000 medical clinics. How many of those are there in your market?
At least where I am selling into medical concerns is significantly difficult, even for institutions that have money. Many institutions operate on tight budgets. So expecting to own the entire market is highly unrealistic. (And yes I have worked on products in the medical industry.) So what is your real expected market share? What is your realistic expected growth rate?
And this of course completely ignores how these places are going to connect to you. The "internet" means that you are going to expose your database directly to the internet. Which is a bad idea and I suspect (hope) that institutions would refuse to do business with that arrangement.
Most performance problems occur due to architecture and design problems. Not technological problems. Attempting to solve serious performance problems with technology is likely to fail because technology only allows for incremental impacts on performance. And this of course presumes you use the technology right in the first place.
To capture what are the Stored procedures are being hit in Production environment the profiler would be used. Whether it would be slowdown the environment? Whether it will affect the performance? If so, what are the alternative to trace the SP hits without affecting the performance?
I get SqlTransaction.Zombie exception in production(In .NET Windows application not ASP.NET application). I got answer in below article how and when the exception is thrown. In production one server application available which perform DB operation and there could be more than one client applications to interact with server.
In the article, it is given that connection is explicitly closed. My question is in real world application what are the possibilities to close the connection (in few cases only it occurs in production)? I would like to hear the possible scenarios to reproduce it.
One of the servers is getting stopped due to the Exception. Please do help.
Is there possibility for SPs to close the connection unexpectedly? If so, please do describe. Thanks in advance.
Neither - I'd use SQL server because that is the database I am most familiar with. If you have no skills in either then look at the support resources for the database. The opinion of a random bunch of geeks is not a good basis for making a decision.
Never underestimate the power of human stupidity
I imported a table called sales to my Oracle database from Access. When I look in the Oracle Application Express object browser, I see the table and I can open it and see the design and the data. However, when I enter the query - select * from sales - I get the error message ORA-00942: table or view does not exist. What am I doing wrong?
I would like to thank everyone in advance for their answers as I am extremely stuck. Also apologies if I put this question on wrong as it is my first attempt at this.
I am currently developing a C# application for a project at work, which uses a SQL 2008 server as a back end database. I know it’s an older way but I have been using windows forms and ADO.Net and have managed through this site and various books to get quit far but now have hit a problem that I cannot find answered on here. Some tables are going to be very large and hence I want to implement paging and have done this through a stored procedure. The application works out what page it requires and passes the start row index and number of rows to return to the procedure. This works perfectly (though I have read various posts to do with performance, and different ways of achieving paging in SQL).
My problem has arisen now that I won’t to introduce searching into the mix. Most posts/articles are geared towards ASP.net application which a user specifies the search criteria and the results for that search are returned in a page form. But I want to copy the functionality of a system we currently run at work called Syspro. Syspro will return you to the page relevant to the data you have just edited, added, or searched for. For example it opens the form with a data grid view on page one, I add new data which will be 100 pages in, after adding the data and closing the add form it finds the page that result is on and shoots the data grid view page to that page and high lights the new row. This works in the same way when you search and edit as you can skip through data on the add/mod form as well.
Is there a way of replicating this behavior in SQL or is this something that is handled in the C# application. I need a way of determining what page the data I require is on, but I understand that SQL only assigns row numbers after a query is run against that table. I have thought of using the primary key to save me the trouble, but some tables will allow deletes.
Is there a way of replicating this behavior in SQL o
Your question about what "behavior" you want to replicate is confusing but yes you can implement paging in SQL.
1. Create your SQL with appropriate search parameters. You should still use parametrized values.
...a. If you have just a couple of items you can hard code the SQL.
...b. With more than a couple items create the SQL dynamically.
2. Apply appropriate ordering to the SQL. This can include creating it dynamically.
3. Apply paging (dynamic SQL again) See the following link
At the business level you might also want to consider what happens to paging if the data being paged changes underneath. Very common answers are
1. It won't, so there is no problem.
2. It won't in relation to the user because the work flow and usage insures that.
Be VERY sure that you analyze this at the business level before deciding that this could be a problem.
Also you should require sufficient search constraints to insure that no single result has lot of pages. Three pages is ok, 100 isn't. If someone claims otherwise then note that users do not randomly seek data. They know what they are looking for. So make them tell you it. Paging is a convenience so they don't have to tell you everything in detail but ignoring it can inhibit rather than help workflow.
Thank you jschell.
But I must apologise as after returning to work today and looking at the programme in which I am trying to copy some functionality from, I have realised I haven’t explained what I am after properly, and fear I have caused some confusion. But asfor what you have told me in the above it validates most of the code I have written, thank you for that.
With that I’ll try again to explain myself, I caused confusion by saying there was a search involved “Apologies”. In a nut shell what I am after is basically “Selecting and displaying a page based on a records location”. Now I know that until a query is run against the table there is no theoretical position of a record. But what the programme does isopen the pageForm on page one of the data in that table. Although there is a ID columnon the table (as I have poked around in the programme files) the page is organised by the first column which is stock-Code. Hence you can page through all the results from a stock code beginning with “A” right through to “Z” which I think is around probably 1000 pages at the minute, not that we go through them all. Then a user opens a new form to edit oradd a new record, when the form is closed and the data returned to the database the pageform will display the page relevant to the stock code added, and you can page backwards and forwards from this page. The same applies to the search, which is conducted in a separate searchForm, which displays the possible results for that criteria, which the user selects one, andreturnsto the pageForm which now displays the page with that record on.
Do you jschell orany one have any idea of how this is accomplished?
i try to learn ado.net so i start with an article how to build database using ado+access and vb.net and think this article is compatible with visual studio 2005not2010 which i have so some error i face like
Me.BindingContext(DataSet1, "table1").Position = 0
i tray toread the first record from access data base
any one can guide me to learn new version of ado.net with ms access