Skip to main content

Create Visual Studio 2010 SQL Server 2008 Database Project

To create the Visual Studio 2010 SQL Database Project, open the Visual Studio (VS) 2010 as a administrator. 
  • Click on File -> New -> Project : In the opened “New Project” window, under installed templates click on Database -> SQL Server and select “SQL Server 2008 Database Project”, select the location and click “OK” button.
  • Open the solution explorer, you will find the database project has been created with the default folders.
  • Expand Schema Objects folder, expand Schemas folder, expand dbo folder and expand Tables folder.
  • Right click on Tables, select Add -> New Item. In the opened New Item window, select Table and enter the name Books, click Add.
  • Double click on added Books.Table.sql script file and include create table script.
  • Right click on Tables, select Add -> New Item. In the opened New Item window, select Primary Key, enter name and click Add. Open the script file and add script to add primary key for the Books table.
  • You can add other scripts under respective folder names like Constraints, Indexes, Triggers etc.
  • Under programmability folder you can add Functions, Stored Procedures, Types, Defaults and Rules scripts.
  • We have added table script and primary key script, now set the SQL server connection string settings.
  • Right click on the project and click on the properties. In the properties page, click on Deploy tab.
  • Set the target database connection, change the Deploy action to create a deployment script and deploy to the database, you can change the other default setting values if you want. 
  • Save the settings and right click on the project and click on Deploy. Check the Output window, the deployment is succeeded or not.
  • Open SQL Server Management Studio, and connect to server localhost. Check the database is created or not. The BookStore database should be created with the table Books.
  • Expand Scripts folder in the project, you will find post and pre deployment scripts. You can include the  post and pre deployment scripts in the Scripts folder.

Labels:

Popular posts from this blog

Error : Task Scheduler - This task requires that the user account specified has Log on as batch job rights

In one of the production environment, we were running with low disk space problem because of the logs. To cleanup the old logs created a  task within the scheduler and have specified "Run whether use is logged on or not". The user account we used was the system logged on user. The task was running fine, after few months as a security policy the password expired. Since the old password expired we had to apply the new password for the task also, but this time we decided to create a new account specifically for the task scheduler with password never expire option. While setting up the new user account and password, run into the below issue: "The task required that the user account specified has log on as batch job rights" To fix the issue follow below steps: From Run type "secpol.msc /s" and enter, the local security policy snap in will open. Select "Local Policies" in MSC snap in Select "User Rights Assignment" Righ...
Read more

ISAPI & CGI Restriction configuration missing in IIS

In windows 7 by default ISAPI & CGI Restrictions are not configured. To enable ISAPI & CGI restrictions, GoTo -> Control Panel -> Programs -> Click on "Windows features on or off -> Expand Internet Information Services - >Expand World Wide Web Services ->Select CGI and ISAPI extensions and Click OK. After enabling, Check in IIS, Open your IIS and the feature will be available. What is ISAPI and CGI restrictions : ISAPI and CGI restrictions are request handlers that allow dynamic content to execute on a server. These restrictions are either CGI files (.exe) or ISAPI extensions (.dll). You can add custom ISAPI or CGI restrictions if the IIS configuration system allows this.
Read more

Implementing Parallelism With A SearchResultCollection

Implementing Parallel.ForEach with a SearchResultCollection: The below piece of code helps to check the given user is a part of the given active directory group. To implement Parallel.ForEach with a SearchResultCollection, do the casting with the SearchResult object and covert it into a list. //// Directory Searcher var directorySearcher = new DirectorySearcher(string.Format("(CN={0})", groupName)); //// Find group var searchResultCollection = directorySearcher.FindAll().Cast ().ToList(); Parallel.ForEach(searchResultCollection, searchResult => {  // enumerate members  var resultPropColl = searchResult.Properties;  Parallel.ForEach(resultPropColl["member"].Cast ().ToList(), member =>  {    var memberEntry = new DirectoryEntry("LDAP://" + member);    var userProperties = memberEntry.Properties;    if (GetUserNameFromProperties(userProperties, "sAMAccountName") == userName)    {      return true; ...
Read more