Iam looking in to buying a new laptop and will need to dual boot Windows and Ubuntu. I am planning three SSD's - one for Windows, one for Ubuntu and one as a shared data drive.
Is it possible to set up DB so that both operating systems can sync to the shared data drive? I have done a bit of research on here and I cannot seem to find a definitive answer.
That post doesn't make sense. You don't need compat formats on the drive system. Dropbox should just be copying down folders and files to the file system irrespective of what format. Any of those will support the same files - for instance, you can dload .docx or linux text files just fine to any format - disk format is irrelevent.
In terms of Dropbox, yes, it does. Dropbox does not support NTFS for Linux, anything other than NTFS for Windows, etc. Are there workarounds? Yes, apparently, but that doesn't make my comment invalid. In reference to Dropbox and how it works, there is no common format that will allow the official Dropbox client to work across mutliple operating systems. I'm not talking hacks or workarounds. I'm not talking about Linux being able to access NTFS. I'm talking naitive Dropbox support of the file system.
Dropbox never officially supported Dropbox being used in such a configuration. They didn't design it to work like that, and if a person wasn't careful they could cause damage to their files or possibly lose data (like by using Selective Sync in such a configuration). I'm guessing that's the reason Dropbox no longer supports their product being used in such a way. They could simply be trying to make it more idiot-proof, like they've been trying to do for years.
I am just trying out your workaround. I hope it works for the computer has been syncronizing for an hour and not yet done. I had 60 GB of data and want to access them from a dual boot Windows-Windows computer. Nevertheless your idea deserved a try. Thanks !
Please note that the above script work and is tested on Linux only. Probably, might be usable also on Mac with some adaptations. There is no any chance to be used directly on Windows! Windows API is completely different and only partially compatible with POSIX (the standard functions used in the C code). Also 'bash' script interpreter is usually not available on Windows, if not explicitly installed.
The drive by noise is dependant upon the position of the noise meter relative to your car , engine speed , engine load and most of all what type of induction you are using - inside bonnet or poking out . Position of the meter can vary from day to day or track to track .
I recorded the normal 98Db static for my car , nowever the drive by noise is measured by a microphone below the gantry on the start / finish line .This for me is about 7500rpm under full load in 4th gear ( about as noisey as it gets ) the recorded level was 107Db
98dba drive by strikes me as being tough for my 7. Even with the extra whisper box on the back the induction is the same. The extra box does not seem to restrict performance any, 2.5" straight through.
I dont think you or me will ever get less than 105 db drive by with your carbs or bodies poking out the bonnet . Unless you cheat of course and lift the throttle , but then many circuits have multiple microphones .......
Make it easier with this script. Mike Petri created a gist that takes parameters for the size of the drive, number of files you want, and the folder path, and generates the T-SQL for you.
Great advice as always, but this is in conflict with the latest Setup Checklist, specifically for the location of the TEMPDB log file. Do you generally advise having the TEMPDB log with the other log files (L:) or with the TEMPDB data files (T:)?
BTW, the effects of these TraceFlags are automatically on in SQL 2016 at this point since MS figured out it would be wise to set them to on and have people purposely set them off if needed instead of the other way around.
Can you expand on this? Why would a full user database data or log file drive be more difficult to restart SQL Server when the solution is to restart the instance which would reset tempdb back to its original size?
Brent, as usual, another great article, thank you. I set tempdb files to fill the drive, both data and log, with virtually no space left over. But I use alerts to notify the team if tempdb fills to 80% of capacity. Relatively easy to implement, too. And, I can grab a snapshot of current workload in the job that is executed when the trigger fires. This seems to meet our needs.
You said to create 8 equally sized data files regardless of the number of cores and provided a link to a KB article that reads:
[QUOTE}
As a general rule, if the number of logical processors is less than or equal to 8, use the same number of data files as logical processors. If the number of logical processors is greater than 8, use 8 data files and then if contention continues, increase the number of data files by multiples of 4 (up to the number of logical processors) until the contention is reduced to acceptable levels or make changes to the workload/code.
[/QUOTE]
Very useful! The Server Setup Checklist (also very useful) suggests putting tempdb log file on the same drive as user log files, but here you suggest putting it on the same drive as your tempdb data files?
Ok got my SSD on my active/passive cluster, followed all steps cluster works great. But, with my 16 core server was going to add files for my tempdb, and when I went to GUI for this the local ssd drive does not show up as an option to add files. Did I miss a step?
I set up tempdb on local SSD storage within a Windows Failover Cluster on SQL Server 2008 by cheating the setup process (for more details have a look on my website). You would have to carefully weigh out if you are willing to go that way as it limits your flexibility and of course is unsupported but it was a valid option for me though.
Why do you recommend a separate partition for the TempDB database files, when adding a MaxSize on each file would do the same trick?
In most organisations, it is a lot easier (for the DBA) to change MaxSize than to ask the storage guys to enhance a partition.
And I do not see any speed advantages to having a separate drive. (Are there any?)
If the database has a table that is occupying 1tb of space, surely that would be the smallest size you would expect the tempbd file to be set to? Especially if the index optimisation job is configured to sort in tempdb?
1. directory organization. ( The individual then suggests we can just create a separate directory on the same drive. )
2. allows a separate IO queue, but is still being sent to the same host kernel/HBA/physical drive array as all the other IO. It really does not provide any performance benefit as the current virtual drive controller already allows a deep queue depth.
Thanks brent for your quick answer. Please answer one last question.
As you said. If I add tempdb file in another drive to let it grow, then will it release space automatically ?. Can I assume that once the use of my tempDB is completed by SQL SERVER, then it will release space automatically or i have to shrink manually when the SQL server does not have any user traffic.?
Our Tempdb is configured according to Best practices. But we have a strange issue. In the one time 100-150 application sessions request the same page in tempdb. And according to sys.dm_exec_requests these requests are from two different DBs (DBs for two different applications)
In an ideal world the OS, logs, data, backup and tempdb should all be on different physical drives as well as volumes. But if limited resources mean 3 or 4 drives instead of 5, which volumes should share a bed?
Hi Brent,
If I a DB which normally is about 140GB, how big the size of the each data file for the tempdb should be? If the drive for the tempdb files is not big enough, can I leave the log file in a different drive? Also If l leave the log file of the tempdb in a different drive than the datafiles of the tempdb, is it necessary for the log file in the same size as the data files?
I just loaded up my Sansa Clip and go the same error message that you recieved. I tried all of the things listed in this thread as well but then decided to just look at the Sansa Clip as any other hard drive and found the answer.
If you manually connect in MSC mode, open the Device Manager and find the Sansa under the USB Root Hub (it may even have a little yellow triangle flag next to it. Right click on the device and select uninstall. Unplug the device and wait at least 30 seconds, then try plugging in again.
I have tried all the solutions on this site to fix my clip . I have found the best way to fix it. You will need a good pair of steel toed boots and a hammer .Lay your clip on a hard surface and hit it as hard as you can with the hammer, them stomp on it with your steel toed boots. This works great, now go out and by a IPOD!!! It is the only thing that worked.
I have tried all the solutions on this site to fix my clip . I have found the best way to fix it. You will need a good pair of steel toed boots and a hammer .Lay your clip on a hard surface and hit it as hard as you can with the hammer, them stomp on it with your steel toed boots. This works great, now go out and by a IPOD!!! It is the only thing that worked.
Disregarding the fact that this solution is excessive over-kill (and probably totally unnecessary in the first place given the assistance provided on this forum and from the available SanDisk Customer Service/Tech Support), I fail to see how the toes (steel or otherwise) of your boots are going to affect the impact of the heels (or soles) on the target device.
I have the very same problem Dannefel has. Despite all the ideas that came up, none worked for me. I wish I could format the sansa player, but how to format something that is not recognised as a usb device on the first place ?
I am unable to try reformatting my player because when I connect to my computer, while it is recognized (not as SansaClip like it used to be, but as Removable Disk F: I cannot right click on the link to that drive. It locks up my explorer panel - essentially just hangs and I have to force a close of my Explorer window.
3a8082e126