Is there a way to determine what application or who might be creating numerous tables in the tempdb. I have one that has grown yet the sp_spaceused command shows the majority of the database empty.
I need to determine where they are coming from and how I can delete them short of stopping and starting the SQL services before it uses up all of my HD.
My Web Host does not provide administrative privilages to the SQL server I have access to. I would like to delete tens of thousands of records from two of my tables without writing to the Transaction Log. Is what I'm trying to do is delete these records quickly without utilizing any of the alotted space my web host has set aside for my transaction log (they give me 50 mb and I go way over that when I run a DELETE statement)
I have some stored procs that have temp table creations in them using "create table #tmptable...". I have noticed that when running the procs, sp_lock shows tempdb system tables being locked. I totally expect this. But, put a PowerBuilder front end on, and I get another situation. Calling the stored procs from PowerBuilder causes the same locks to occur, but they are not released after the data is displayed through the application. Furthermore, this blocks other users from creating anything in tempdb until the user logs off of the application and ends the connection to the database.
please help - is there something I am missing in my procedures, or is this a PowerBuilder issue?
Im sure this is something minor that I am overlooking but for some reason when I go to debug my ssis package all these windows keep opening( callstack, watch1, watch2,watch3,breakpoints, etc) . I cant seem to find out how to disable these -- any suggestions? I dont remember actually setting these to run
Can anyone point me in the direction of a script that incorporates sp_addlogin, which allows for adding 200 sql authentication logins from an excel spreadsheet, or a temporary sql table with the id info, containing the username, password, and def db?
I'm trying to avoid adding each new login one by one. EXEC sp_addlogin 'username', 'password', 'default database'Thanks, BPH
What is a more efficient way of doing the following such that DATEDIFF() does not have to calculated numerous times?
CASE Â WHEN DATEDIFF(DD, @Today, COALESCE(POS.[PurchaseDate], POS.[FinalizedDate])) <= 0 THEN '<= 0D' Â WHEN DATEDIFF(DD, @Today, COALESCE(POS.[PurchaseDate], POS.[FinalizedDate])) > 0 AND DATEDIFF(DD, @Today, COALESCE(POS.[PurchaseDate], POS.[FinalizedDate])) <= 7 THEN '> 0D AND <= 7D' Â WHEN DATEDIFF(DD, @Today, COALESCE(POS.[PurchaseDate], POS.[FinalizedDate])) > 7 AND DATEDIFF(DD, @Today, COALESCE(POS.[PurchaseDate], POS.[FinalizedDate])) <= 30 THEN '> 7D AND <= 30D' Â [code]....
I am new to Sql Server [Express version] and am not even sure I'm making the right choice. So here I am, seeking advice.
My database needs are nothing sophisticated. They just involve: (a) create tens of thousands of separate data files each under a unique file name of up to 8 characters, with file names read in from a pre-determined file name list. (b) store/insert VOLUMINOUS numerical data into each of the data files, with the data indexed by date&time, plus maybe one or two additional character or string fields. (c) for each data file, retrieve a subset of its data, perform extensive numerical calculations, and then store the results in one or more separate corresponding files, e.g. if a file name in (b) is F12345, (c) creates F12345R1, F12345R2, F12345R3, etc. which stores different sets of calculated results.
Thus, this is purely a console application, doing a batch job, and requiring no graphical user interface. Both automation and speed are important here, due to the large number of data files that must be created and/or updated, and the very extensive numerical calculations on the data.
The goal is to automate the daily or weekly creation of each of the tens of thousands of Sql Server database files, insert fresh data (read in from a fresh ASCII file) into each file, numerically process the data and then store the results in one or more separate, corresponding result data files, with all the steps automated and without need for GUI. Once coding is done, the entire data processing session is expected to run for many hours, or even days, in an automated manner, and without human intervention.
What would be the most efficient way of doing this under Visual Basic Express (which is what I'm learning to use) by directly calling Sql Server Express without having to go through GUI to create database files? What is the proper interface utility or library to use to enable direct database function calls without the need to learn SQL language? Is Visual Basic and/or Sql Server even good choices for what I want to do? I want to be able to call the basic, simple database functions directly and simply from program code in a non-GUI, non-interactive manner for the tens of thousands of separate data files that will be used.
I really miss the good old days when one can do a straightforward batch job via a console application, with simple, direct calls to create new data files, insert and index fresh data, retrieve any subset of data to do extensive calculations, create new files to store the results, etc. all under automated program control and iterating through unlimited number of data files, until the job is finished, all without human intervention during processing.
Or am I missing something because all this can still be done simply and easily under VB and Sql Server? I've several books here about Visual Basic 2005 and Visual Basic 2005 Express, all showing how to create a database via a GUI utility. That's fine if one needs to create just one or two databases, but not hundreds, or even tens of thousands (as in my case) of them on the fly.
So, I am looking for the simplest and most direct database interface that will allow me to do the above under VB program code alone, and easily. For something as simple as I have described above, I don't think I should have to learn the SQL language or manually create each database file.
As you can see, I just want to get some heavy duty numerical processing job done over tens of thousands of data files as simply and efficiently as possible, and with as little fanciful detour as possible. So, ironically, I am trying to use Visual Basic without being cluttered by having to learn its "Visual" aspects, yet GUI is what most VB books devote to or emphasize heavily. Similarly, I would much rather use simple, "lean and mean", direct database function calls than having to learn a new vocabulary of "English-like" SQL language.
Yes, I'm not used to this tedious detour of learning the GUI aspect of VB, or learning the Structured Query Language of Sql Server, just to try to do something simple that I need to do in batch mode via a console application.
Are there any good books or other helpful URLs that will help a guy like me? Am I even using the wrong language and the wrong database to do what I want to do? What are the better alternatives, if any? Any advice, experience and pointers on any of the above issues raised would be very much appreciated. Thank you!
I encontered a problem which did not allow me to select any thing from the temparary tables of the tempdb database. (e.g one of the temparary tables is #239E4DCF), why is that and how can we solve this problem? As I urgently need to look at this tempdb database, it is full. I am looking forward to hearing from you and thanks a lot in advance for your help.
I have a table that has company id, attachment file name, folderexists columns.
First what I need to do is create a series of folder or directories on a networked server using the company id as the folder name where the folder name does not already exist.
Second I need to move files based on attachment file name and company id to the proper folder.
For those who want to know, this is a remediation project because of a bug in our application.
The application is supposed to created the folder based on company id and then put the attachment in that folder.
"tempdb is skipped. You cannot run a query that requires tempdb"?
We're running a .Net web application with a SQL Server 2000 backend, and we get the error intermittently. Restarting the SQL Server service seems to fix it, as it causes tempdb to be rebuilt, but this isn't a long term solution. Any direction or hints would be greatly appreciated. Thanks! - Mike
I'm new to my company, although not new to SQL 2005 and I found something interesting. I don't have an ERD yet, and so I was asking a co-worker what table some data was in, they told me a table that is NOT in SQL Server 2005's list of tables, views or synonyms.
I thought that was strange, and so I searched over and over again and still I couldn't find it. Then I did a select statement the table that Access thinks exists and SQL Server does not show and to my shock, the select statement pulled in data!
So how did this happen? How can I find the object in SSMS folder listing of tables/views or whatever and what am I overlooking?
THis is sql server 6.5 question. I have tempdb data device size default 2 MB, which has completely filled up. I am trying to expand data device to it. I created new device tempdb_data_ext (250 MB) and tried to expand tempdb data device. But everytime I do it, it ends up adding space to tempdb log device. How can I expand tempdb data device?
Hi, How can I control the growth of tempdb in SQl server.It's growing like anything. CAn I create some alerts or jobs and what those alerts/job are supposed to do? All help appreciated. Jai
Hello! This is error message I discovered in NT even viewer: c:MSSQL7DATATEMPDB.MDF: Operating system error 112(There is not enough space on the disk.) encountered.
In SQL Server error log the errors are: Error: 1101, Severity: 17, State: 10
Could not allocate new page for database 'TEMPDB'. There are no more pages available in filegroup DEFAULT. Space can be created by dropping objects, adding additional files, or allowing file growth..
Currently tempdb rezides on C drive and it's almost out of space. What should I do? Detach tempdb and then move to different drive? What's the procedure?
TEMPDB in one of our production servers does not clear up so every three to four weeks I have to restart NT. Nothing like this happens on any of the other three servers. Does anybody know where I should look at to correct the problem. I sure would appreciate it. Thanks Shashu
I have never done this before and thought I would ask. Is it possible to detach the tempdb database, move it to another drive or partition, and then re-attach it? What would be the downside or side-affects to doing such a thing?
Error : 933, Severity: 22, State: 1 Logical page 258 of the log encountered while retrieving highest timestamp in database 'tempdb' is not the last page of the log and we are not currently recovering that database.
I use sqlserver -T4022 to start my SQL Server since it will not start with out it. When I start sqlserver without the option, it tells me that
Error : 615, Severity: 21, State: 1 Unable to find database table id = 2, name = 'tempdb'.
I need to move tempdb to another drive,also increase the size.Largest database is 15GB.Can anyone suggest the size and also the exact commands to move.Do I need to backup the databases before I do this task?If SP1 is not installed,will it be o.k for me for this tempdb problem.If we have a larger tempdb like 4GB,will it effect anything?...Urgent!!
I read an article on this site by Michael Hotek re "Basic SQL Server 6.5 Configuration Options". In the paragraph about TempDB he says that you should always avoid using Temp tables in stored procs. I use this feature a lot when trying to do "not in" type queries (I filter out a portion of a larger table and then use the "not in" on the temp table rather than the entire table.) Is there a better way to run a Not in query. I have the table well indexed (i think) but it seems to do a full table scan if I use the entire table.
Our Tempdb.mdf file is 11 gigs. I have tried several things to shrink this but with no luck. Does anybody have a suggestion on how I can free up that space. I have tried to re-start Sql but that didn't do anything. I thought that there was a bug, if the files got above 4 gig that sql wouldn't clear them, but I could be wrong
I thought I could detach it, and attach a new file, but makes me nervous without knowing if that’s correct.
I am trying to configure a 6.5 server to set the tempdb to run off disk. I reset the tempdb in ram = 0 in the configuration, and restarted the service, but it left it as running in ram, with 0 configured. I then rebooted the server, and it still left the tempdb in ram. Any ideas?
I am trying to get some information about tempdb database. I've tried BOL but I couldn't find a whole lot of info. I am trying to find out what size should tempdb be to not to cause problems. Also, I am trying to shrink tempdb by using shrink database option in EM, but it only shrinks the tempdb transaction log not the datafile, and I don't know why it is happening.
We are using Peoplesoft HRMS version 7.0 on NT Server 4.0 and SQL Server 6.5, service packs on both up-to-date.
The server is a HP LX Pro with 4 200 MHz 1MB cache processors with 2,560 MB of RAM and 18 9GB drives configured with different combinations of RAID 1, 1+0, and 5.
The database is 2.3GB in actual size with the specific size of 6GB for data and 2GB for log on separate RAIDs.
We would like to use tempdb in RAM to boost the speed of complex queries that use the tempdb for intermediate working tables.
We would like to know of any experience of running tempdb in RAM, issues to overcome, of how to setup.
There are articles and books not recommending using tempdb in RAM. Comments anyone?
Note: Have looked in SQL Server DBA Survival Guide, and SQL Server Unleashed, along with the normal MS Documentation, technet, online books, and knowledge base searches.
Everything I've ever heard or seen says not to put tempDB in RAM, citing reasons of negligible benefit or even worse performance as it steals memory from SQL's cache memory.
My issue is I need to take anywhere from 500 to 3000 records (games played) in a batch every five minutes from a table, ordered by game id. There's no guarantee of sequential order to how the records are inserted, so I need to do an ORDER BY in my query. I also do a stored procedure for ranking that requires an ORDER BY.
The performance difference between the two is staggering. 1000 records with a 200 mb tempdb database (not in RAM) takes about 300 seconds. With a 16 MB tempdb database IN ram, it takes just under 127 seconds. Only problem? I'm constantly getting, after a few batches have run, "out of space in syslogs for tempdb ram messages. "
Is there a way to net such performance from tempdb without putting it in RAM, and if not, is there a way to explicity clear out tempdb. Thanks for any help.
I have a problem with Tempdb database on SQL 6.5 server.....when i create a temporary table, i block other users in other databases. Actually i run a stored procedure which creates a temporary table and then the procedure insets some values of a table from my test database. When the spored procedure is executed, users in other databases also get blocked and no new user will be allowd to log on to the server. When i check as to what the other users are executing, i find that they are also creting or droping a temp table. So i will have to either kill my SP or let it finish and continue blocking other users.
As of now, i am not able to find a reason for that and i try to run the Stored procedure in offpeak hrs.
I have not played around much with Temp tables in SQL 6.5. Pl do suggest me as to what to do....
Some details you would be interested on :
Server - SQL Server 6.5 Front End - Great Plains Size of Tempdb - Data Space Available( It says shared with data) database_name database_size unallocated space ------------------------------ ------------------ ------------------ tempdb 1502.00 MB -6301.82 MB
I have a dumb ? When I go in to expand the tempdb to at least 25mb req. for the migration It is actually expanding the Log size & the Db available size still says 1.76mb.