Sometimes Task->Generate Scripts takes too time to backup especially when you want to backup only selected tables in the database. This can be done easily with bcp, issuing the command in your power shell dumps the data in tab-delimited values into a file. \> bcp "DATABASE.dbo.TABLE" out "C:\Downloads\TABLE.sql" -c -S "HOSTNAME" -U USERNAME -P PASSWORD Hope this helps, this is very useful for migrating data and for seeders where some tables are only needed to be seeded into the database as dependent values for other tables. We are heavily using this technique for testing. As for reference, here's our use case Dump data into .sql files Seed using QueryFromFile Run automation; this can insert new values to other tables based from the seed data from .sql file Rollback new values We need to rollback each time since we want to have data the same as it was so we can run each time and expect the same results for our testing. If not, there should be err...
Today, I embarked on a mission to set up an IIS server on our local network. The primary objective? To create local network versions of our applications for testing and development purposes. Additionally, we're in the process of setting up a CI/CD server to automate our workflows. However, like many journeys, this one had its share of hurdles. The initial hiccup arose when I realized that .NET was installed before IIS, leading to compatibility issues. Despite attempting to install IIS through the control panel and tweaking .NET components, the problem persisted. "Nada." After some trial and error, a breakthrough emerged. The solution? Executing dism as an Administrator in the C:\Windows\Microsoft.NET\Framework\v4.0.30319 directory: \> dism /online /enable-feature /featurename:IIS-ASPNET45 /all And just like that, the clouds parted, and the path forward became clear. With IIS up and running seamlessly, our developers rejoiced, and testing commenced with renewed vigor. H...