I'm storing time series data in a table in SQL server 2000. The tablehas columns like: CodeEquity, PriceDate, LastPrice. To extract thelast price for a number of equities on COMMON DATES I have used thequery:select t.LastPrice,h1.LastPrice,h2.LastPrice,h3.LastPrice fromBlg_HistoricData t,Blg_HistoricData h1,Blg_HistoricDatah2,Blg_HistoricData h3where t.CodeEquity=114151 and h1.CodeEquity=112220 andt.PriceDate=h1.PriceDate and h2.CodeEquity=112580 andt.PriceDate=h2.PriceDate and h3.CodeEquity=112228 andt.PriceDate=h3.PriceDatethis works for about 20 self joined tables and then says syntax error.I'm wondering what sql limits it hits. Is it possible to do this inSQL for 300 tables?Thank you.
I have used this mysql code in my programm before:
select * from address order by vorname asc limit 0, 10
It works fine. But now I want to use sql server, and it doesn't recognize the term limit. So I have found out that I can use top instead. I have changed my code into this:
select top 0 * from (select top 10* from address order by vorname) order by vorname asc
I was wondering what more experienced DBAs have observed with regard to the capacity of a MSSQL DB. Is there an upper threshold of rows where performance becomes unacceptable? I have a fairly slow, but constant input rate of approximately 2,000 rows every 60 seconds or so (that is a little high, but I'm interested in worse case scenario here). That is up 172,800 rows a day. (I'm being overly pessimistic here.) We'd like to be able to keep all of this around as long as possible.
Or would a more heavy duty DB be in order for these sorts of data rates?
Hi, I need some help about a project I'm working on.
I'm working on a project (based on MS SQL Server) that will involve a lot of clients, each one constantly querying the server. Just to have an idea of the project, I'm talking of about 2000 clients, each one queries the database 3-4 times per second: a total of 6-8000 queries per second. The database is reached through Internet and every client uses a dedicated DSL connection.
My questions are: - What is the maximum workload of a Microsoft SQL Server? - What happens when the server workload reaches 100%? is there a queue? and what happens when the queue is full? is it possible that the server goes out of service due the excess of work? - What are (more or less) the hardware requirements for such a server?
can anyone help me, at least telling me how to find these answers (web sites, books, ...)
SQL Server 2000 SP3 on a Dell dual 2.4GHz Xeon box 3GB RAM Windows 2KSP4. Two aplication dbs, each less than 2GB in size.Had a problem where we would run Solomon queries and what not againstthe box. It had 2GB RAM, and sqlserv.exe would take up to 1.85GB ofRAM, exhausting the physical RAM on the box. SQL would choke and theSolomon users would have problems, and I would have to restart the SQLservice.I added another GB of RAM, bringing the box to 3GB, and increased thepaging file. The OS sees it, and SQL sees it. I check EnterpriseManager, and tell SQL to dynamically configure memory, and it offers anupper limit of 3071MB, so it "sees" the 3GB.I can stress the box with queries to the point that sqlserv.exe takes1.99GB of memory (as viewed through Task Manager) and then SQL serverchokes. It never goes past 2GB, and the OS and box continue runningfine.Does SQL server 2000 have some upper limit, or do I just need to changesome setting through EM?Thanks.
Hi all, I know that you can save a DTS package to SQL Server (localpackage under Data Transformation Services in the EM).I wonder can I limit which login has the right to save DTS package? Imean, I would like logins with sa right to have this right but not forother ordinary logins.Can this be done in SQL Server?
Hallo!I have small or big problem.I want creat Store Procedurs whit limit rows.For example I need rows from 100 to 200.--Select * from tableHow I doing best way.
hey all, i want to know Equivalent of "LIMIT" of MySQL in SQL Server 2005? in mysql we can direclty get data using LIMIT clause. my question is how to do this in sql server 2005? thanks.
One of our database is approaching the gigabyte size. I know that microsoft claims to support terabyte databases with sql server 7.0. I was wondering if anyone could tell me about the max size of database they have used on an OLTP site without running into problems. ofcourse with SQL Server.
On the MS website (at this URL: http://www.microsoft.com/sql/evaluation/overview/default.asp) it says that the Standard edition of SQL Server 2000 has a database size limit of 1,048,516 terabytes.
Talking to a friend, he tells me this is not true, and that it has a database size limit of 12gb.
Is Microsofts site incorrect, or is my friend lost?
I am being told that the colid in syscolumns may not exceed 255 if the table is replicated. Is that true? Where in BOL or elsewhere can I read-up on this? This is a shocking development!!!
I am about to start working on a project where I would be required todynamically create linked servers during the execution of anapplication. One of the requirements is for the Link Servers to becreated and dropped before and after the retrieval of the data. Myquestion is about any type of cap on the number of linked servers SQLServer 2000 can have registered at any single time. If I find out thatthere is some type of cap, I would need to look into another way todeal with my linked server needs. Thanks for any help/information youmight be able to provide.
Has anybody encountered a physical size limit for a sql server 2000 transaction log running on win2k?
Transaction log reached ~6Gb before rolling back the delete stating transaction log was full. There was 42Gb free on the server and the log was set to unlimited growth.
We have applications connected to SQL using windows authentication. While having connection with Application user can also access to Database instance on the same time as well. We need to limit the access of user outside application.
I am looking at running SQL Server 2005 Standard Edition in a clustered environment (2 nodes) and am not sure if the 4 processor limit applies to the number of processors per node or the number of processors it will run on in the entire cluster. Could someone please clarify this for me?
SQL Server 2012.If I create a table with 307 columns, all of type nvarchar(50), it works. If I add another column of type nvarchar(50), it works but I get a warning:
Warning: The table "RowSizeError" has been created, but its maximum row size exceeds the allowed maximum of 8060 bytes. INSERT or UPDATE to this table will fail if the resulting row exceeds the size limit.
307 x 50 = 15350 and 308 x 50 = 15400. why I get the warning below with 308 columns but not with 307?
drop table [RowSizeError] go CREATE TABLE [RowSizeError]( [F1] [nvarchar](50) NULL, [F2] [nvarchar](50) NULL, [F3] [nvarchar](50) NULL,
I have a simple SP that returns 2 columns with 4 inner joins, results are about 100 odd rows max, nothing complicated. When I run the SP via SSMS it works fine, as soon as this is run via an application server the SP fails to complete with the error :
Internal error: An expression services limit has been reached. Please look for potentially complex expressions in your query, and try to simplify them.
We are not getting anywhere near the expression limit so I cannot understand why we are suddenly receiving this error. 2 weeks ago this query was running fine, no updates have been rolled out to the SQL database servers or application servers but the error is suddenly appearing on both prod and dev environments.
Our development team wanted to create a database user for each application user in the application and use these for granular data access control, which at first, sounded like a good idea but our initial testing ran into some interesting results.
Our target user base was about 15 million users with an estimated 1% concurrency rate, and finding no MS documentation on an upper limit to the number of users a database can have we began some load testing to see how the database performed. In the hundreds of thousands of users range our test database had a hard time performing well under light loads (even without any concurrent connections).
When we purged the users and reverted back to just a handful of service accounts, performance went back to "normal" under the same loads. I began to wonder if this is a situation where throwing more hardware at the problem would overcome the issue or if there is a practical upper limit to the number of users a single database can handle well.
(There were of course other cons to this arrangement and I certainly was never going to expand the users tree in the object explorer for a database like this, but we thought it a solution worth investigating.)
What is the largest number of users any of you have had in a single database?
Hi,I have successfully set and used a linked server to query ADSI.Since this question also concerns MSSQLServer, I've cross posted it --I hope this is not a breach of etiquette.I have successly created a view based on the linked server.Unfortunately, it only shows 1000 records, and there does not seem tobe any way to set the Page Size.I found the following:http://support.microsoft.com/defaul...kb;en-us;243281Which seems to imply that the default can be set by changing registrykey: "HKEY_CURRENT_USERSoftwarePoliciesMicrosoftWind owsDirectoryUI"I have set this key, and also set it for the user account under whichMSSQLServer runs. The value persists after a reboot. The Domain Grouppolicy sets the default to 15000.This behaviour is not restricted to the linked server. If I use thescript found here:http://hacks.oreilly.com/pub/h/1121 I can access morethan 1000 records, but only if I set the "Page Size" property. If Icomment it out to let the default hold, it is 1000.It must be settable SOMEWHERE or the whole linked server thing is ofvery limited use.At present, the best solution I've been able to come up with is to usethe above script modified to run as a DTS package. Yuck.TIA,BM
Thanks in advance. What is maximum SQL Server database (*.mdf) file size with SQL Server 2000 as part of Microsoft Small Business Server 2000? (Database files were limited to 10 GB in SBS 4.5 with SQLServer 7.0... has this changed?).