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
I have a situation where I would like to move the physical location of the Model, tempdb and MSDB database files. Does anyone know of a way to do this?
View 2 Replies View RelatedHi All,
I am working on a third party client product which shrinks all the databases in MS SqlServer based on the rule or parameter that is set. This product will be used in production server which has MS SqlServer 7.0.
My question is: Is it advisable to shrink Master,Model and Msdb databases in an production environment? Please give the reasons.
Thanks
Sri
When 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
How to move master , model and msdb database to some other location. Can we overwrite the master, model and msdb files
Hi all
What is best Disaster/Recovery methode to securing the system databases.
Master database allows only Full backup
MSDB allows Full ,Diff
Is there a way to move my mdf and ldf files for the tempdb and the model databases? If yes, how? I tried ti detach but SQL Server will not let me.
View 1 Replies View RelatedDB replication can set db recovery model to simple ,why db mirror can not db recovery model to simple.
DB mirror must be set to full recovery model.
As far as I know, whatever db mirror and db replication ,there is a log reader to read the log in the ldf file DB mirror and DB replication are almost the same principle to replicate the db to another db server.
We're just in the process of moving to 7.0, although SQL 7 has the autogrow feature we'd prefer to size MASTER and MSDB properly in the first place to avoid disk fragmentation. Does anyone have an experience/suggestions as to appropriate sizes, particulary for MASTER?
View 5 Replies View RelatedLate last Sunday I had to do an emergency rebuild of our SQL Server (v2012). In my haste, I neglected to restore the MSDB and MODEL DBs, and am instead using those which came with the fresh SQL install -- which obviously don't contain my jobs and maintenance plans. Would there be any problem/conflicts with me restoring those DBs this weekend?
View 5 Replies View RelatedI have a server attached to a SAN, all user db's are on the SAN, master, tempdb, and msdb are on the local machine. We will be replacing the machine (not the SAN) to a newer sql server. Our plan was to create the new server with same name, deattach current user db's,backup master and msdb, then connect new server with same name an IP to SAN. I then wanted to restore the master and msdb db's to the new machine, and attach the user db's. We are running log shipping to a stand-by server in this configuration. I was thinking I could let last tran log backup and copy occur, and then let the last restore happen on the standby. I would then shut down the agent. Should I not be able to restore the MSDB and master to the new server (as long as all file folder locations are the same) and be ready to go? Or are there issues when restoring the Master and MSDB to a new server from a different server.
View 5 Replies View RelatedHello:
I am in the process of setting up a dbcc checkdb and dbcc newalloc job for the user database in production. Do I need to include master and msdb to have checkdb and msdb run against them daily?
Any information you can provide will be greatly appreciated. Thanks.
David Spaisman
Will I encounter any issues running DBCC CHECKDB on either msdb or master?
Thanks!
Hi All
Will Rebooting the SQLServer 2000,Is it change recovery model of MSDB Database
Please help...
On a 2008r2 server, I ran the frag utility against master and msdb and noticed they were severely fragmented.
Is it ok to defrag them using the standard Alter Index command?
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 Replies View Relatedthanks
View 7 Replies View RelatedHi All,
Anyone know how to change the directory of system dbs --- master and model dbs? Thanks.
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)
I was contacted by the SAN team to test backup/restore of larger databases using a split-mirror backup (BCV) or clone that is taken from production db server and copied to another sql box. They want to use this process once a week. I see the mounted drives with the data/log files. All looks good. Initially I attempted to attach the databases and received (Unable to open the physical file db.mdf Operating System Error 5 Access is denied). I manually granting SQLServerMSSQLUser$<computer_name>$<instance_name> on all of the physical files 20 total. That worked.
Since this will be weekly, the SAN team performed the copy again and now none of the databases can communicate with the newly copied files. NTFS permissions need to be set again. I'm getting (Operating System error 21: the device is not ready). Is there something that I'm missing in this process how the vendor BCV clones the data and SQL communicates with the copied files as I was thinking it would be more automated process?
I have a 2 node cluster having 4 cores each wherein having 3 instances of SQL 2008 R2 enterprise comprising of 60 databases, 20 on each instance. I need to setup mirroring for each of the databases to a secondary server having 4 cores and 3 instances.
What i understand is that in this case the mirror server will be providing max of 512 worker threads and the 60 mirror databases would consume 240 threads.
What all needs to be checked for looking into the feasibility of going ahead with a async mirror setup as mentioned above.
hi folks
Ive 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 dont 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 doesnt seem to be happening.
any ideas?
much appreciated
N.
Hi All,
I took a backup of master,model and msdb database which was on D: drive and i tried restore it on C:. Now if i try to start sql server it comes out with a erorr that model database cannot be found and it keeps looking for model in D: drive which is not there.I tried restore of model with move option but it says cannot drop model as its system database.I tried attach detach but it does not understand tempdb as temp db is also on d: and i cannot understand how to move or point it to c:
Suggestions will be greatly appreciated
Vishal
We have an install of SQL MDS 2016 CTP3 which I can access via the web browser and create models etc. I have uninstalled the Excel add-in for 2012 and installed the MDS 2016 CTP3 add-in on Excel 2010. I am able to create a MDS connection and the "Test" reports success in Excel.
However, when I try to connect to a model via the Master Data Explorer to load an entity, Excel hangs with the message "Loading objects for xxxx_Model". My only option is to close Excel via the Task Manager.
Where do I look for more detailed logs? Is there a switch I can use to provide a better debugging experience?
Can i have a combination of sources some with Unique Identifiers and some without?
I need to know what happens when I have option “Create Code values automatically” selected for the entity and same time pulling Unique Identifier for other sources in same entity stage table.
When we select option “Create Code values automatically” for the entity we creates, then during load from external source to MDM stage we don’t send any values to MDM stage “Code” field and in next step when we execute the stored procedure to load the data from MDM stage to MDM model, it assigns the Code values to each record in MDM stage and MDM model.
I need to know whether after executing the store procedure, will it assign Code values for only NULL records in MDM stage and not give us any error for the records that already have Code values present in MDM stage.
Hi,
When i create a new table in Model database how can i automatically create table in other user databeses. Thanks for your answers
When creating databases is it a good idea to use the master.dbo.sysdatabases database and then create databases under this.
View 4 Replies View RelatedMy company is new to MDS. I am trying to set an attritube in an entity to read only so the users can't change the value in that field. When I did that, the whole model disappeared. I thought I had deleted it by accident so I created a test model and tried to do the same. The test model disappeared. This time, before saving the new settings I took a snapshot. After saving I took another snapshot. You can see that the whole model is gone (zz_RN_Permissions_Test). I tried every other coworker with admin rights and nobody shows it on the Models list. The behavior on the Excel add-in is correct. I can't change any values on that column. But I need to keep the models available.
See before and after snapshots below.
We are designing a new data model, and have many clients. Currently they each have their own database in SQL.
We are contemplating the pro's and con's of migrating to a Single Master Database.
I would like to hear from others on what your thoughts are on the pros and cons. Also, if you have experience doing something similar, please speak up.
Thanks in advance,
ScAndal
When I create a database, is there a way to make sure that the default recovery model is Full instead of Simple?
View 1 Replies View RelatedHow do you hide the default system databases so that they cannot be viewed? Also when it it time for me to access them how do I unhide the databases?
View 1 Replies View Related