I launched ClearTeam Explorer for the first time but I can't find how to setup snapshot views... Where are they located in the desktop CTE application? I see dynamic and web views only.
Thank you
Update 2015:
As mentioned below, since ClearCase 8.0.1.6 (Dec 2014), snapshot views are supported (release notes):
CTE support for snapshot views
ClearTeam Explorer (CTE) now supports snapshot views.
For more information, refer to the following technotes:
1691355: new features in CMAPI
1691375: about deliver/rebase operations
1691401: known issues
(original answer April 2014)
Web views are considered snapshot in CTE.
The difference is that the view server cannot reside on your local workstation: it only resides in the CTE server.
See "Using ClearCase Web views" and "About ClearCase views" for more.
A Web view is a copy-based ClearCase view that is tolerant of high-latency connections to a CCRC WAN server, although it may be used in both wide-area network (WAN) and local area network (LAN) environments.
Many of the ClearCase operations you can perform using Web views require an explicit connection to a CCRC WAN server. However, a subset of operations are available that can be used, even when you are disconnected from the CCRC WAN server.
(This is the part similar to a snapshot view:)
A Web view uses a config spec to select a specific set of file and directory versions from one or more VOBs so that you can access them on your computer.
Resources under source control must be loaded into a Web view before you can access them.
Prior to 8.0.1.6 release ClearTeam Explorer supported only web views (over WAN) and dynamic views (over LAN). However, from ClearCase 8.0.1.6 release onwards, ClearTeam Explorer client supports snapshot views (over LAN). This means that locally registered snapshot views will be listed under My Views node in ClearTeam Navigator view. So you can browse through and perform source control operations on snapshot view resources. For more information, refer http://www-01.ibm.com/support/docview.wss?uid=swg27037036
Related
Similar to this question, is there a way to visually display a database view in a database diagram?
Yes, though not using SSMS's Database Diagrams.
My solution for this is Microsoft BI's Data Source View (DSV). This requires that you have Microsoft's BIDS (Business Intelligence Development Studio), a component of SQL Server Standard (or higher) installed.
BIDS 2005 through 2016 should all work and provide the same basic functionality.
Alternatively, if you want access to a free version of the toolset, you can download and install SQL Server Express with Advanced Services ( basically SQL Express with Reporting Services added), though I have not worked with this version to verify.
With BIDS installed, launch it (or Visual Studio, if you have a more full version installed)
Go to File > New Project
In the New Project dialog, under Templates, expand Business Intelligence and choose a project. (I believe any BI project type will do. If you don't see any BI Projects, then you most likely do not have BIDS installed or at least installed with that version of Visual Studio).
Provide a location for this project to live on your machine.
Click OK to create the Visual Studio and BI Project.
In the Project Explorer pane, right-click the Data Sources folder and select New Data Source. Follow the Data Source "wizard" to create a connection to your desired data source. In the 2014 (and other?) version of BIDS, there is a question about the security credentials you'd like Analysis Services to use to connect to the data source. If you are just wanting to create a DSV for diagramming only, it doesn't matter what you select here.
Right-click the Data Source Views folder and choose New Data Source View. A Data Source View wizard launches.
Using the wizard, add the tables and views you would like to see in your data source view to the Included Objects pane using the left and right arrows.
Click Next to complete the table/view import and to give your DSV a name.
Click Finish to launch the import and see your initial diagram.
You now have a database diagram that includes both tables and views.
Here's a DSV of Microsoft's AdventureWorks2008 OLTP database. This image shows an example of what one can do with SQL views in DSVs. In it, I replaced the Employee table with the vEmployee View (gave it a friendly name of 'Employee') that exists in the database, and added logical primary key and foreign key relationships that mirror the PK/FKs of the underlying physical table.
Note that all changes made in a DSV are logical and therefore isolated to the DSV file itself and do not impact the database directly.
Developers are working in two different locations in differents countries, instead of having one TFS db in one location (and others connecting from another place), is it possible to have 2 replicated sites of TFS2010, each on a different server and some kind of nightly synchronisation?
We support this scenario with TFS Proxy. It stores a local cache of Version Control data on the remote location.
There is no counterpart for Work Items.
Replication is possible, because it is just a SQL Server feature. But you will have lots of conflicts during the synchronization. It is not a supported scenario, and not recommended.
We're developing an aspx project with Visual Studio 2010 Professional, SQL Server 2008 R2 and Team Foundation Server 2010. Since the development is being carried out in multiple offices, each developer has their own local instances of the databases.
I want to bring these multiple databases under source control (or at least the schemas of the DB, structure and stored procedures - data doesn't matter to me). My preferred approach is to add database projects to the VS solution, which is already source controlled in TFS. Any changes will be distributed by TFS, and can be deployed locally.
The problem I'm having is that the database projects contain a reference to a local database instance (server & name). When someone gets the latest version of my changes, they will have a reference to my local DB instance (which is different to their local DB instance). They would need to change the DB details (thus checking the dbproj out) in order to get my updates.
So, is there any way that the database server & name can be left out of source control while the schemas remain under source control? Any help would be much appreciated!
I'm not sure if you can. However, you could use an alias, so all of the developers use a database on their local machine, but referenced by the same alias.
Take a look at: http://www.mssqltips.com/sqlservertip/1620/how-to-setup-and-use-a-sql-server-alias/ for how to set an alias up.
That way you can separate the database from the connection details.
I'm involved in developing a unique enforced database source control solution called DBmaestro TeamWork.
It has a plugin to SSMS which allows the developer to work directly on the database objects (change their working environment), run their tests and then perform Check-In which reads the metadata (tables' structure, procedures, functions, views etc.) to the version control repository.
With the Impact Analysis it is easy to merge changes from different databases to a single database.
The impact analysis algorithm perform 3-way analysis (not just a simple compare & sync) to identify changes origin from developerA which should not be reverted when developer merge his changes and it ignores the database name when running the impact analysis or generating the delta script.
Can we use GIT as the source control for sql management studio?
for Database source control within SSMS
Agent SVN - SCC Subversion Plug-in.
http://www.zeusedit.com/agent/ssms/ms_ssms.html
or
http://www.red-gate.com/products/sql-development/sql-source-control/
I’ve found out that ApexSQL has a tool that natively supports Git as a source control system. It comes as a SSMS add-in, and offers a wizard you can use to map database objects with the source control systems. To do that:
Download and install ApexSQL Source Control
Start SSMS and in Object explorer select the database you want to be linked to a source control
Right-click the database, and form the context menu, select the Link database to source control option, from the ApexSQL Source Control submenu
Select the source control system (in your case it is Git) and choose from 2 database development models - shared or dedicated. Shared model is recommended when you link a database on which multiple developers will work at the same time
Filter objects which you don’t want to track using source control: by schema, type or name by schema, type or name
Provide appropriate login information and repository string. For Git it is:
<protocol>://<hostname>:<portnumber>/<Git server name>/<repository> (see example below):
More detailed step-by-step instructions can be found in this article:
http://knowledgebase.apexsql.com/link-database-source-control-system-2/
You could add Git Bash as an External Tool (Tools | External Tools...):
Name: &Git (use & to specify a hot key)
Command: C:\windows\SysWOW64\cmd.exe (32-bit Command shell)
Arguments: /c ""C:\path\to\Git\bin\sh.exe" --login -i" Finding the path where Git is installed on a Windows system
Initial directory: $(ItemDir)
Try sql-source-control, a free and open source CLI used to get SQL into source control systems like Git.
https://www.npmjs.com/package/sql-source-control
Microsoft has released SQL Operations Studio. It's a free tool that runs on Windows, macOS, and Linux, for managing SQL Server, Azure SQL Database, and Azure SQL Data Warehouse; wherever they're running. It comes with native GIT support.
Since SSMS is (more or less) a custom version of Visual Studio, you might be able to use a solution intended for VS:
Using Git with Visual Studio
Alternatively, manage your DB source code in Visual Studio from the beginning, not in SSMS. That way (at least in VS2010) you have database projects, integrated deployment and unit testing etc. Or continue using SSMS and check in your code from an external tool when you're ready (not so convenient, of course).
But it depends on exactly what you're doing: SSMS is a DBA tool, VS is a developer tool. Either way, you should be using some form of source control, but it's not clear from the question exactly what sort of files you need to version.
Not yet but if you go to http://redgate.uservoice.com/forums/39019-sql-source-control/suggestions/537681-add-git-support and vote for redgate to add support for git it might get added in the next version. Yes I know it's a commercial product but some products are just good enough to pay for!
Red Gate SQL Source Control has been updated to include Git and Mercurial support (as well as Perforce and TFS). Be forewarned that their DVCS integration is not 100% feature complete in relation to their SVN product, as basic features such as viewing history of an object are not supported from within SSMS. This may be a deal-breaker if other Red Gate tools like SQL Compare are part of your workflow.
Our workaround was to install TortoiseGit or GitExtensions and navigate to the repository on disk to drill into the specifics. It works but is a bit clunky.
VersionSQL is an SSMS source control add-in I've designed to be lightweight and easy to use. In the Object Explorer panel, just right-click on a database or object and click Commit. VersionSQL will script it out to Git/SVN in a neatly organized folder structure.
Check it out at https://www.versionsql.com
There have been a number of answers around this question which you might want to look at but in a nutshell ....
The nature of version control is to store the original file and then the deltas, the difference between the original file committed and and subsequent changes (ok i have made that a bit simpler than it is perhaps) and then to manage the version number and give tools to extract any particular revision you need. This also then allows you to compare previous revisions and roll back (etc. etc.)
The RDBMS is made up of the schema and the and data these change and can change frequently in the case of the data so even if you did VCS what would you compare to do a restore and how would that help? Assuming you have a live system then reverting to an earlier revision would lose all the data stored in the interim and although i have never tried it i suspect could destroy the general integrity of the RDBMS.
The better solution is to use a backup application built for that RDBMS, MySQLdump say in the case of MySQL which makes a snapshot of the data and the structure of the data and store that in a safe place.
Dumps can be scheduled regularly and you can do things like master/slave databases (or other strategies) so you can backup live production databases on the fly without impacting on performance
i have an access front end. the backend is a sql server database. can i have users download the runtime and have the full functionality of being able to edit the sql server database from the access front end? why is it free? what makes it different from the whole version?
In a nutshell, the Access Runtime version allows you to distribute an Access Database application to machines that do not have Access or Office installed. It won't allow you to open the database in design view or to make any changes to the database apart from adding or editing data. They can contain the data tables or can be set up using linked tables so that you have a central database (in some cases a shared .mdb file on a network, or something like SQL server)
Because many Office 2007 installations are not the professional version (Home and Student, Small Business etc) which does not include Access, making the runtime freely available is to encourage Access Developers to build databases which may be used in such cases or even in instances where office is not installed at all.
See: Running in Runtime vs. Full Access 2007
In a nutshell, the runtime version allows you to change data but not objects (forms, reports, queries, etc).