I have a install of SQL 2005 that is about 5 months old. The tempdb.mdf and master.mdf files have ballooned to a huge size almost filling my hard drive. How do I reset them to a reasonable size?
View 14 RepliesI was able to find a few posts on this topic, but none of them quiteseemed to fit the situation, so I'm hoping that someone else might beable to help me here.I have a client who is using SQL 2005 (sorry, don't have the exactbuild with me). They run a weekly process which causes TempDB to growto over 100GB before it fails due to a full disk. Once it's grown tothat size we can't seem to shrink it again short of restarting theserver.The database is set to Simple recovery mode and I believe that it isset to auto shrink.Here are some things that found out/tried:DBCC SHRINKFILE (tempdev, 50000) does nothing.DBCC OPENTRAN returns no transactions.If I look in TempDB for any temporary tables, I get a couple dozen.They all have zero rows in them though. I didn't think to look at thecolumns that they contain, but maybe that will give me an indicationof their use. I used SELECT OBJECT_NAME(id), rowcnt FROMtempdb..sysindexes WHERE OBJECT_NAME(id) LIKE '#%'sp_spaceused shows that almost none of the space is actually beingused.I've looked for reindexing operations in their code and didn't seeany, but there's quite a bit of code there. While there are someoperations against some very large tables, I didn't see any obviouscartesian products or sorts either. Again though, there's a lot ofcode and I haven't profiled much of it.My plan right now is to reboot, set up a trace to track both filegrowths and SQL statements and then see if I can find whichstatement(s) are causing the TempDB to grow to be so large. Anysuggestions on additional things to track? Even given this though, Idon't know if that will help me with the shrinking issue, except topossibly prevent it from being necessary in the future.Any advice or suggestions welcome. Please let me know if I've left outany important information. I always seem to forget at least oneobviously important bit of information. :-)Thanks!-Tom.
View 2 Replies View RelatedHi,
We're running our database on SQL Server 7 and we've setup the tempdb to grow automatically.Gradually,it has grown upto 11390 MB and the used space is only 14 MB.It's not shrinking when we used the shrinkdb option.We cannot move the tempdb to RAM as it's very big.Can anyone help us in this...
How do you shrink the tempdb in SQL Server 7 after you allocated a large space to it but later realized you allocated too much.... I need to reclaim the space allocated to it but when I try to change the size or do a shrinkdb it either tells me I cannot shrink it smaller than allocated size or it shrinks tempdb to current (which is too large)... I looked online but could not find anything...
Any suggestions or assistance would be much appreciated... up to my eyes in tempdb..... Bill.
Hi Guys,
Tempdb in one of our SQLSERVER is standing at 5GB. I try to shrink it to 2GB, using following commands.
DBCC shrinfile(2,2000)
DBCC SHRINKDATABASE (tempdb, 2000)
It doesn't want to shrink at all... I ran sp_spaceused it give following results
Reserved data indx_size unused.
808 KB 384 KB368 KB 56 KB
I dont understand why tempdb doesnt want to shrink...?? help is greatly appericated.. thanks..
Does tempdb ever need to be shrunk, or have it's log (does it even have one) dumped or does sql server handle this chore?
View 2 Replies View RelatedOne of my boxes was built with all of the system databases on the C: drive, and tempdb is up to 2 GB and there is no room left on the drive
It should have been installed on the D: drive
I've never had to do this before, mostly because I never install sql serevr on the c partition
Any war stories or suggestions
Hello friends..
We are getting below error every day.we have job Shrink TempDB which runs every hour..but once a day we are getting this error.Is this error becasue of other jobs also running by that time which uses huge resource from DB..I cant understand why???.. can any body have an idea??
Executed as user: NT AUTHORITYSYSTEM. ...97031). The PageId in the page header = (1:1056620160). [SQLSTATE 42000] (Error 8909) Table error: Object ID -720718983, index ID 0, page ID (1:297030). The PageId in the page header = (1:-1839155936). [SQLSTATE 42000] (Error 8909) Table error: Object ID -720718983, index ID 0, page ID (1:297029). The PageId in the page header = (1:1057229472). [SQLSTATE 42000] (Error 8909) Table error: Object ID 0, index ID 0, page ID (1:297023). The PageId in the page header = (0:0). [SQLSTATE 42000] (Error 8909) Table error: Object ID 0, index ID 0, page ID (1:297022). The PageId in the page header = (0:0). [SQLSTATE 42000] (Error 8909) Table error: Object ID -720718983, index ID 0, page ID (1:297021). The PageId in the page header = (1:1056467424). [SQLSTATE 42000] (Error 8909) Table error: Object ID -720718983, index ID 0, page ID (1:297015). The PageId in the page header = (2:1071640160). [SQLSTATE 42000] (Error 8909) Table error: Object ID -7207189... The step failed.
Papillon
I have a problem with my TEMPDB Database.It gets extra size throughimporting data into one of my databases in same server.How can I shrink my TempDB Databse?Thanks
View 1 Replies View RelatedHi,
I'm running Sql 2000 with many users logged in. My tempdb database has grown to a large size 3/4 of it free space. Is there a way to shrink the database while users are logged on. I tried using the enterprise mgr. to shrink the tempdb database, but it did not work. How can I shrink this? It's using a ton of free space.
Thank You in advance
I have a tempdb that was created at 1Gig. I don't know why but I want to shrink it below the original creation size. Is there a way to shrink this file or create a new file and delete the old?
I have tried shinkfile and shrink database with no luck.
Thanks Jeff
A customer on SQL7 has a 40GB tempdb (which is usually 2-5GB) which has filled the drive. ShrinkDb/ShrinkFile do nothing as the db has only 2GB of free space. How can I truncate the data or blitz tempdb and create a new (2-5GB) one (Stopping the server, deleteing the .mdf, starting the server creates a new tempdb with the same size as the old one!)
View 2 Replies View RelatedHow do you shrink the tempdb in SQL Server 7 after you allocated a large space to it but later realized you allocated too much.... I need to reclaim the space allocated to it but when I try to change the size or do a shrinkdb it either tells me I cannot shrink it smaller than allocated size or it shrinks tempdb to current (which is too large)... I looked online but could not find anything...
Any suggestions or assistance would be much appreciated... up to my eyes in tempdb..... Bill.
--------------------------------------------------------------------------------
Hi Everyone!
A customer installed a SQL 2005 production server and due to a configuration error chose a minimum master db size of about 1GB! The master database resides on the system partition and causes problems with a service pack installation, so it should be shrinked and moved. Until now I was unable to find a way to shrink the master db, although 99% of its space is unused (as one might expect.)
Is there a way to deflate the master db without doing a reinstall?
Thanks for any tips!
I need a script to Backup & Shrink tempdb.
namesize
tempdev1024
templog64
tempdev21024
tempdev31024
tempdev41024
tempdev51024
tempdev61024
tempdev71024
tempdev81024
I can't believe how many tempdb's there are?
Output of below query is
SELECT session_id,
SUM(internal_objects_alloc_page_count) AS task_internal_objects_alloc_page_count,
SUM(internal_objects_dealloc_page_count) AS task_internal_objects_dealloc_page_count
FROM sys.dm_db_task_space_usage where internal_objects_alloc_page_count >10 and session_id> 50
GROUP BY session_id;
[Code] ....
Database MDF is 27806 MB and I tried to shrink but unable to shrink. It is production server.I do not want Restart sql server.There is no open transaction.
thanks
View 7 Replies View RelatedWhen SQLserver2K was installed it placed master, model, msdb, tempdb data files in the installation location (i.e. C:Program Files....). This puts pressure on the C: drive, which also holds the page/swapfile. I want to move at least the tempdb location to the new 'Default data directory' and log directory we set after installation (i.e. E:MSSQLData).
How do I get tempdb to relocate to E: given that it gets recreated each time SQLserver starts?
TIA,
Al
Is it possible to encrypt Master database and tempdb? On executing below query result is showing temdb is encrypted.
SELECT db_name(database_id), encryption_state, percent_complete, key_algorithm, key_length
FROM sys.dm_database_encryption_keys
I am interested to hear if people think it would be a good idea to movethe Master & TempDB to a different HD.Here is my DB Server's set up:1. Processor: (1) AMD XP 28002. 1st HD (IDE 0) is the system & boot drive3. (3) SCSI HD make up a hardware RAID level 0 (striped withoutparity)solution - these striped drives are just for my working DBs4. (1) SCSI HD that's not doing anything.I want to put the Master & TempDB on the SCSI HD that's not doinganything. Would that be the best place for it for maximum performance orshould I put in the striped array. I am leaning more towards putting onthe SCSI HD that's not doing anything. What do you all think?Ed*** Sent via Developersdex http://www.developersdex.com ***Don't just participate in USENET...get rewarded for it!
View 1 Replies View Related
We had an issue last night where tempdb ran out of space on one of our servers. Upon investigation I found that SSMS was reporting only one data file assigned to tempdb. I knew this couldn't be the case and dove into the system tables to figure out what is going on. I found what appears to be data corruption. There are a number of file records that appear in the master.sys.master_database_files that do not appear in the sys.database_files table in tempdb.
I tried to add files that it showed already existed and they of course errored out. I restarted SQL Server to get tempdb rebuilt and that did not work either.
Has anyone else ever ran into this? What was the resolution?
Here are some queries to demonstrate what I am seeing. Terrible formatting I know, but I don't know of a better way.
/*------------------------
select * from master.sys.master_files where database_id = 2
select * from tempdb.sys.database_files
------------------------*/
database_id file_id file_guid type type_desc data_space_id name physical_name state state_desc size max_size growth is_media_read_only is_read_only is_sparse is_percent_growth is_name_reserved create_lsn drop_lsn read_only_lsn read_write_lsn differential_base_lsn differential_base_guid differential_base_time redo_start_lsn redo_start_fork_guid redo_target_lsn redo_target_fork_guid backup_lsn
----------- ----------- ------------------------------------ ---- ------------------------------------------------------------ ------------- -------------------------------------------------------------------------------------------------------------------------------- ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- ----- ------------------------------------------------------------ ----------- ----------- ----------- ------------------ ------------ --------- ----------------- ---------------- --------------------------------------- --------------------------------------- --------------------------------------- --------------------------------------- --------------------------------------- ------------------------------------ ----------------------- --------------------------------------- ------------------------------------ --------------------------------------- ------------------------------------ ---------------------------------------
2 1 NULL 0 ROWS 1 tempdev E:MSSQL$S1MSSQL.2MSSQLDATA empdb.mdf 0 ONLINE 524288 1280000 128000 0 0 0 0 0 NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL
2 2 NULL 1 LOG 0 templog E:MSSQL$S1MSSQL.2MSSQLDATA emplog.ldf 0 ONLINE 128000 268435456 64000 0 0 0 0 0 NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL
2 3 01E3A12D-9CC1-44B6-B077-947C45BD5FDC 0 ROWS 1 tempdb_Data_01 K:MSSQL$S1Data empdb empdb_Data_01.ndf 0 ONLINE 524288 -1 0 0 0 0 0 0 50000000011100001 NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL
2 4 4E91B5E8-1EE9-4DA1-985F-A37CB7262BC6 0 ROWS 1 tempdb_Data_02 K:MSSQL$S1Data empdb empdb_Data_02.ndf 0 ONLINE 524288 -1 0 0 0 0 0 0 50000000013400001 NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL
2 5 125B73CC-A6EB-464E-A8B8-50269EFD1311 0 ROWS 1 tempdb_Data_03 K:MSSQL$S1Data empdb empdb_Data_03.ndf 0 ONLINE 524288 -1 0 0 0 0 0 0 50000000015700001 NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL
2 6 6C4CDA80-4AF0-42FE-BFCF-4E6AEF97956A 0 ROWS 1 tempdb_Data_04 K:MSSQL$S1Data empdb empdb_Data_04.ndf 0 ONLINE 524288 -1 0 0 0 0 0 0 50000000018000001 NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL
2 7 360F5EE6-5207-402E-BFFC-88F2B4532DD2 0 ROWS 1 tempdev_11 S:MSSQLDATATEMP empdev_11.ndf 0 ONLINE 512000 1280000 128000 0 0 0 0 0 1347000000109400212 NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL
2 8 60F262B1-32AC-433C-95CE-8450BBFA2247 0 ROWS 1 tempdev_12 S:MSSQLDATATEMP empdev_12.ndf 0 ONLINE 512000 1280000 128000 0 0 0 0 0 1348000000169600151 NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL
2 9 A18FA498-37A6-4A52-ABA6-C915FD50123E 0 ROWS 1 tempdev_13 S:MSSQLDATATEMP empdev_13.ndf 0 ONLINE 512000 1280000 128000 0 0 0 0 0 1349000000001600060 NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL
2 10 2DC2BCCC-3DD8-45D3-B454-5DB88D0B6783 0 ROWS 1 tempdb_Data_05 K:MSSQL$S1Data empdb empdb_Data_05.ndf 0 ONLINE 524288 1024000 65536 0 0 0 0 0 50000000020400001 NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL
2 11 06A09B39-09C7-41C6-B11A-BEC1785039B0 0 ROWS 1 tempdb_Data_06 K:MSSQL$S1Data empdb empdb_Data_06.ndf 0 ONLINE 524288 1024000 65536 0 0 0 0 0 50000000022700001 NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL
2 12 14F1019E-B3FE-4B7C-827B-880D3E0C430C 0 ROWS 1 tempdev2 I:MSSQLDATATEMP empdev2.ndf 0 ONLINE 256000 640000 65536 0 0 0 0 0 103000000037600078 NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL
2 13 743D3EC0-8011-4ECC-8CA6-256C65B37FC5 0 ROWS 1 tempdev3 I:MSSQLDATATEMP empdev3.ndf 0 ONLINE 256000 640000 65536 0 0 0 0 0 103000000043000001 NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL
2 14 968C0C01-95C9-4EA2-97B6-0DEFBBB8FEB5 0 ROWS 1 tempdev4 J:MSSQLDATATEMP empdev4.ndf 0 ONLINE 256000 640000 65536 0 0 0 0 0 108000000039000001 NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL
2 15 D4551A7F-3998-41E3-81B5-627168CBE77A 0 ROWS 1 tempdev5 J:MSSQLDATATEMP empdev5.ndf 0 ONLINE 256000 640000 65536 0 0 0 0 0 108000000041400001 NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL
2 16 701E5614-E61C-46CB-8D23-F8726B6B1F4F 0 ROWS 1 tempdev6 S:MSSQLDATATEMP empdev6.ndf 0 ONLINE 256000 640000 65536 0 0 0 0 0 114000000013600081 NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL
2 17 B4AB50DF-8004-4CBA-B97F-683BD8791FF4 0 ROWS 1 tempdev7 S:MSSQLDATATEMP empdev7.ndf 0 ONLINE 256000 640000 65536 0 0 0 0 0 114000000019200001 NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL
2 18 C0A50693-6311-4F33-B20B-6C030CC4F65F 0 ROWS 1 tempdev_14 S:MSSQLDATATEMP empdev_14.ndf 0 ONLINE 512000 1280000 128000 0 0 0 0 0 1349000000279900070 NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL
2 19 800B86A7-142F-46C9-984F-8673CEFE2DDD 0 ROWS 1 tempdev_01 S:MSSQLDATATEMP empdev_01.ndf 0 ONLINE 512000 -1 128000 0 0 0 0 0 1350000000553600232 NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL
2 20 4A008D1B-89E1-4F07-AB5C-CADBFB6ABE44 0 ROWS 1 tempdev01 F:MSSQLDATA empdb empdev01.ndf 0 ONLINE 524288 -1 128 0 0 0 0 0 78000000008100001 NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL
2 21 B6B63467-4179-47FD-A226-58639B92F402 0 ROWS 1 tempdev03 T:MSSQLDATATEMP empdev03.ndf 0 ONLINE 524288 -1 0 0 0 0 0 0 234000000253600164 NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL
2 22 2A075CBA-C600-47D9-B6B1-8231743EC5AF 0 ROWS 1 tempdev04 T:MSSQLDATATEMP empdev04.ndf 0 ONLINE 524288 -1 128 0 0 0 0 0 234000000262600001 NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL
2 23 EDAFB1FB-3B3D-4F7E-B335-8056F2FA9EAD 0 ROWS 1 tempdev1 F:MSSQL$S1DATA empdb empdev1.ndf 0 ONLINE 524288 -1 0 0 0 0 0 0 453000006813300252 NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL
2 27 1BFE36F9-B621-4B7C-99C8-0C262ADFFEF9 0 ROWS 1 tempdev02 F:MSSQLDATA empdb empdev02.ndf 0 ONLINE 524288 -1 0 0 0 0 0 0 430000003795400001 NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL
2 29 7C8D9FDF-E2D9-4274-BC3D-B2EC060C4B39 0 ROWS 1 tempdev_02 S:MSSQLLOGTEMPDB empdev_02.ndf 0 ONLINE 524288 -1 0 0 0 0 0 0 4030000039691100043 NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL
2 31 60973FF9-A35F-433C-9E58-D29F00E4D5A7 0 ROWS 1 tempdev_03 S:MSSQLLOGTEMPDB empdev_03.ndf 0 ONLINE 524288 -1 0 0 0 0 0 0 4033000048392400207 NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL
2 32 506E7E19-4D0A-47D8-A687-C9658500F367 0 ROWS 1 tempdev_04 S:MSSQLDATATEMP empdev_04.ndf 0 ONLINE 524288 -1 0 0 0 0 0 0 4033000048449300130 NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL
2 33 4DFD4A82-FD5C-4CEE-8939-C01C596B3714 0 ROWS 1 tempdev_05 S:MSSQLDATATEMP empdev_05.ndf 0 ONLINE 524288 -1 0 0 0 0 0 0 4033000048515100001 NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL
2 34 B6A34F7D-7FBD-460F-B6FF-ACED575FE2D4 0 ROWS 1 tempdev _06 S:MSSQLDATATEMP empdev _06.ndf 0 ONLINE 524288 -1 0 0 0 0 0 0 4033000048659000118 NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL
2 35 4B33C871-B52E-4514-8EBB-E856F151A96D 0 ROWS 1 tempdev_07 S:MSSQLDATATEMP empdev_07.ndf 0 ONLINE 524288 -1 0 0 0 0 0 0 4033000049131800087 NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL
2 36 40575107-6C34-408A-BF04-DDF7D71935BE 0 ROWS 1 tempdev_08 S:MSSQLDATATEMP empdev_08.ndf 0 ONLINE 524288 -1 0 0 0 0 0 0 4033000049137600001 NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL
2 37 C1DCC4CF-740A-4EB6-AF2E-7B105477251F 0 ROWS 1 tempdev_09 S:MSSQLDATATEMP empdev_09.ndf 0 ONLINE 524288 8192000 524288 0 0 0 0 0 4035000024325400202 NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL
(32 row(s) affected)
file_id file_guid type type_desc data_space_id name physical_name state state_desc size max_size growth is_media_read_only is_read_only is_sparse is_percent_growth is_name_reserved create_lsn drop_lsn read_only_lsn read_write_lsn differential_base_lsn differential_base_guid differential_base_time redo_start_lsn redo_start_fork_guid redo_target_lsn redo_target_fork_guid backup_lsn
----------- ------------------------------------ ---- ------------------------------------------------------------ ------------- -------------------------------------------------------------------------------------------------------------------------------- ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- ----- ------------------------------------------------------------ ----------- ----------- ----------- ------------------ ------------ --------- ----------------- ---------------- --------------------------------------- --------------------------------------- --------------------------------------- --------------------------------------- --------------------------------------- ------------------------------------ ----------------------- --------------------------------------- ------------------------------------ --------------------------------------- ------------------------------------ ---------------------------------------
1 NULL 0 ROWS 1 tempdev E:MSSQL$S1MSSQL.2MSSQLDATA empdb.mdf 0 ONLINE 524288 1280000 128000 0 0 0 0 0 NULL NULL NULL NULL 95000000084000037 11815719-7EBA-453D-B93C-1CA083FADA76 2007-10-30 10:00:02.263 NULL NULL NULL NULL NULL
2 NULL 1 LOG 0 templog E:MSSQL$S1MSSQL.2MSSQLDATA emplog.ldf 0 ONLINE 128000 268435456 64000 0 0 0 0 0 NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL
(2 row(s) affected)
hi folks
I€™ve had a SQL 2000 server restored (using Veritas 9.1) to another server also running SQL 2000. I now have a collation problem.
When trying to add users to a database, I receive a "Error 446: Cannot resolve collation conflict for equal to operation" message.
I noted that tempdb and user tables collation don€™t match - so I was going to change the user tables. However, the master collation doesnt match tempdb, model or msdb.
Server is set to SQL_Latin1_General_CP1_CI_AS
Master - SQL_Latin1_General_CP1_CI_AS
tempdb, model, msdb - Latin1_General_CI_AS
I was under the impression that when tempdb was recreated it inherited the master database's collation? This doesn€™t seem to be happening.
any ideas?
much appreciated
N.
Hi Guys,
Since,You cannot mirror the master, msdb, tempdb, or model databases.What will happen if i create new login,change existing security profile and new jobs,change of existing job on princicpal db. how these will be mirrored to other server and in case failover, how it will treat.
Thaks
If you have problems shrinking a transaction log no matter what commands you issue, here's a way to shrink the tranlog:
1. Right click on the properties of the database and go to the options tab.
2. Change the recovery mode to simple.
3. Right click again on the database - go to all tasks - shrink database.
4. Shrink the database.
5. Change the recovery mode back to what you had it as.
I found this out by trial and error as I could not find any documentation on it and no matter what I tried, I could not get the transaction log to shrink.
Has anyone seen the SQL Server error:
"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 got a File with sales orders and their details.
Step 1. First I am filtering the Sales Order information and inserting it in my Sales Orders table.
Step 2.Then I am filtering the details from the sales Order and inserting them in the respective table.
My Problem is that the Sales Order File does not contain the Sales Order key (ID), this is generated by the SQL Server. How can get it in order to use it in the second step? I need it because it is a foreign key in the details table.
Any Idea?
Hello,
I'm new to SQL and need help with a query. Not sure if this is the right place.
I have 2 tables, one MASTER and one DETAIL.
The MASTER table has a masterID, name and the DETAIL table has a detailID, masterID, and value columns.
I want to return a populated MASTER table with entries based on the DETAIL.value.
SELECT MASTER.*
FROM MASTER
WHERE DETAIL.value > 3
This is a simplified version of my problem. I can't figure out how to set the relationship between MASTER.masterID and DETAIL.masterID. If I do an INNER JOIN, the number of results are based on the number of DETAIL entries. I only want one entry per MASTER entry.
Hope this makes sense.
How can I do this?
GrkEngineer
I have a SQL 7.0 sp3 server and I am trying to shrink a production database for use on other servers. The database/log sizes are 9601mb / 138mb with 772mb / 128mb free. I truncate a table that contains binary data. After this the database/log sizes are 9601mb / 138mb with 6634mb / 111mb free. The next step is to use EM to issue a shrink db. After this the database/log sizes are 6807mb / 378mb with 9.56mb / 365mb free.
After the use of truncate the the data in the datafile is about 2967mb.
After the shrink db the data in the datafile is about 6797mb.
The size of the data grew after the shrink db was issued. I looked at the tables and the space is largely associated with two tables that have a binary field, but the number or rows are still the same. I ran a checkdb just to make sure that there was not a problem and no problems were reported. I have used this process many times and this is the first time I have come up with these results. Any suggestions?
Thanks,
Glen
if I shrink the db will it enable me to create another db with that space released by the first db?
View 1 Replies View RelatedHow can i shrink my log file? It is like 900 megs and i
was it to be more like 400 megs.
Please Help
Melissa Sener
Project Manager
Square Yard
Hi, My name is Alexander and came´s to ask about Sql Server log.
Do you know why sometimes the log not truncate? All time
comes increasing!
I setup "Automatic Shrink" and it swims happens. If you can help me!
Thanks in advanced
Hi everybody:
Actually I have a 8.5 Gb database but the correct size that I need
to due disk space is 5 Gb. When I make a backup, the size of the dump is
4Gb, so I wonder if I create a 4- 4.5Gb my dump db will fit in it, but
not. Other way is create antoher db with 4 - 4.5 Gb and transfer via
sql-transfer or sql-bcp but I got a message that my device is too
short.
So I ask : What are the correct ways to reduce the size of a
database ?
Thanks in advance.
Hello,
We just migrated our DB from one SQL Server to Another. Both DB's used to be the same size at 11GB. The new SQL Server is a whopping 33GB, and I can't seem to find out why. The new DM has fewer tables (the data is identical).
Does anyone know how I can compact or shrink my DB, know why or how it grew so much and didn't go back down to normal size, and maybe where I can search properties or change settings to find out what is going on and prevent it from happening again.
I know MS Access has a shrink utility, but don't know where it is in SQL Server.
Thanks, in advance for your help.
Rodney