My case is
Input is "abdknmgbm".
The record in database that i want to query out is "abkdnmgmb"
The input and database record is quite similar.
String length is same, only some arrangement of character are not same.
In the above case, dk and kd ; bm and mb.
How i write query for this string searching?
Help and Thanks.
Actually the swap char will not always are char 3 and 4 and last 2 chars.
For example it may also be like this :
Input: " abcdkazbmopdkubmgt "
The wanted result is : "abckdazmbopkdumbgt"
Input and wanted result length are same.
BUT the input string length is not always the same.
Very hard to solve this. Tq.
If you think it will do what you need you can write a function in C# or VB and add it to SQL Server (I assume you're using SQL Server). As to how to add it to SQL Server, I'd rather write a tip than post it here.
Given that the function has the signature int Levenshtein ( string , string ) you would then be able to say:
SELECT * FROM sometable WHERE dbo.Levenshtein ( somefield , @somevalue ) < @somethreshold
The threshold should probably be based on the lengths of the strings, for instance half the length of the shorter string.
To make things more efficient, you could write a function with the signature bool IsSimilar ( string , string , int ) that will return false as soon as the Levenshtein Distance between the strings exceeds the threshold (the third parameter).
SELECT * FROM sometable WHERE dbo.IsSimilar ( somefield , @somevalue , @somethreshold ) = 1
Hi everyone! I need to know the maximum number of concurrent connections to SQL Server 2008. When I check from Server properties in Management Studio, it is set to zero with a text description that zero means unlimted connections.
I cannot comment on the number of connections, but in your design, you might want to consider a 3 Tier approach where each client does not have a direct connection to the database; only the middle tier would connect. This would greatly reduce the number of connections to the database.
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?