I have a SQL Server database that had a binary field that stored photos used in profiles and articles. We've moved this to the filesystem rather than storing them in the DB and now the database queries are faster. The size of the database didn't change (it's roughly 30GB). I think almost all of that space isn't needed anymore and the DB may be 10GB without the photos. Should I compact / shrink the db? I heard this isn't good to do but in this case, maybe it is. I won't be storing the photos in the DB going forward either so not sure if it will ever reach that size again.
Delete that column from you table and then schedule a rebuild index to run during the night or a period that no one is using the database. After rebuild finished run the following command that will only
More than 75% of all records are compromised because of the loss or theft of a privileged credential. Experts have been exploring Active Directory infrastructure to identify key threats and establish best practices for keeping data safe. Attend this month’s webinar to learn more.
Load balancing is the method of dividing the total amount of work performed by one computer between two or more computers. Its aim is to get more work done in the same amount of time, ensuring that all the users get served faster.
Using examples as well as descriptions, and references to Books Online, show the documentation available for date manipulation functions and by using a select few of these functions, show how date based data can be manipulated with these functions.