SQL Source Control 2003 - FAQ

Visual SourceSafe integration and comprehensive database documentation.
The awarded solution avaliable for Microsoft SQL Server developers, that enables source control and comprehensive documentation of your databases by Visual SourceSafe integration.

Frequently Asked Questions

If you cannot find answers for your questions here, ask us at info@skilledsoftware.com.

See Releases history for the full fixes list.

Do I need any other software to use SQL Source Control™ 2003?
Do I need to install server-side software to use source control functionality?
What happens when someone ALTERs database item using 3rd party software (for example QueryAnalyzer)?
Application errors after clicking [Finish] in the New Connection Wizard
Application errors when using Windows Authentication on remote SQL Server
Empty database objects (tables, views etc.) node in connections pane
I have a problem with placing my order
My application hangs when running on workstations with .NET Framework 1.1 Beta installed
"Argument 'Length' must be greater or equal to zero" error on WITH ENCRYPTION procedures
I cannot open the BPF file that is present in Source Safe project
"Access denied" on save
"QueryInterface for interface SourceSafeTypeLib.IVSSDatabase failed" on new instalation
Performance problems when using Norton AntiVirus package realtime monitor feature

Do I need any other software to use SQL Source Control™ 2003?

Yes. SQL Source Control™ 2003 works with Microsoft SQL Server and Microsoft Visual Source Safe. See requirements section for the full software list.
Do I need to install server-side software to use source control functionality?

No. SQL Source Control™ 2003 requires no additional server-side software to be installed to use any of its functionality.
What happens when someone ALTERs database item using 3rd party software (for example QueryAnalyzer)?

If you want to use an external SQL editor, you should check the database item out in SQL Source Control before editing and check it in after making changes to the database. Please note, that SQL Source Control checks in the most current database state, which is not always the code that is currently visible in SQL Source Control edit window (for example when developer changes it outside SQL Source Control).
However we strongly advice to deploy SQL Source Control on all your development workstations, to get the most of teamwork development.
Application errors after clicking [Finish] in the New Connection Wizard

On some systems, that does not have .NET Framework SP2 installed, clicking [Finish] in the New Connection Wizard might result in:

Error Source : System.Windows.Forms
Error Number : 5
Error Description : Specified argument was out of the range of
valid values.
Parameter name: index
Error Module : frmVSS_Process.AddConnectionTreeItem
[v.1.0.1107.23698]

To fix that problem, please apply .NET Framework Service Pack 2, download it here.
If you don't know what is your .NET Framework version, read this article.
Application errors when using Windows Authentication on remote SQL Server

When you create connection to a remote SQL Server using Windows Authentication, the application shows an error.

Skilled Software confirms that is a problem in SQL Source Control 2003. The fix for this issue is included in the current release.
Empty database objects (tables, views etc.) node in connections pane

On some databases the evaluation version of the software does not display the list of the first 5 database objects, if after they alphabeticaly ordered there are 5 or more system database objects present at the beginning of the list.
This issue does not apply to a commercial version of the application.

WORKAROUND:
Create database objects that appear in the top 5 list in SQL Enterprise Manager.

FIX:
Skilled Software confirms that is a problem in SQL Source Control 2003. The fix for this issue is included in the current release.
I have a problem with placing my order

Please try our separate FAQ located on Customer Care Center page.
My application hangs when running on workstations with .NET Framework 1.1 Beta installed

This issue applies to .NET Framework version 1.1 only. .NET Framework version 1.1 is currently in Beta state and Microsoft does not support it right now.

FIX:
This issue has been fixed in the 2003-01-27 release.
Beta versions are far more unstable than final releases and cannot be relied on in a production environment, we strongly recommend installing .NET Framework 1.0 with SP2 applied.
.NET Framwork version 1.0 application installed on a system with both 1.1 and 1.0 of the Framework will run against 1.0 unless an administrator changes this behavior.
"Argument 'Length' must be greater or equal to zero" error on WITH ENCRYPTION procedures

When you try to access encrypted stored procedure (WITH ENCRYPTION), the application raises an "Argument 'Length' must be greater or equal to zero" error.

FIX:
This issue has been fixed in the 2003-01-30 release.
I cannot open the BPF file that is present in Source Safe project

This behaviour is by design. The BPF file taken from the Source Safe project is not the same as the BPF file, that is created by using "Save project (As)" menu command.
Beginning from 2003-02-01 release the Source Safe configuration file extension has been changed to .bpfconfig

To save a SQL Source Control project file for later use, you need to:

1) Create the project
2) Save it to a disc location using "Save project (As)" menu command
3) Try to re-open it from that location

The inner structure of the BPF project file should contain XML code. The files that are put automaticaly to Source Safe are always 36 bytes long and contain the "[BPF Source Safe configuration file]" string.
"Access denied" on save

Sometimes when user tries to save the file (locally or to the database), the local file save may fail with the error message:
Access to the path ... is denied

FIX:
This issue has been fixed in the 2003-02-01 release.
"QueryInterface for interface SourceSafeTypeLib.IVSSDatabase failed" on new instalation

This error message may appear for new SQL Source Control 2003 instalations:

QueryInterface for interface SourceSafeTypeLib.IVSSDatabase failed

FIX:
Please check that you have Visual SourceSafe client tools installed on your workstation. The most often install location for this is "C:\Program Files\Microsoft Visual Studio\Common\VSS\".
If you have Visual SourceSafe client tools installed, you need to re-register SSAPI.dll, that is needed by SQL Source Control 2003 by running:

regsvr32 <SQL Source Control 2003 instalation folder>\win32\ssapi.dll

in the Windows command prompt. You may also need to copy ssus.dll from <Visual Source Safe instalation folder> to <SQL Source Control 2003 instalation folder>.

Visual SourceSafe client tools are required for SQL Source Control 2003 to run.
Performance problems when using Norton AntiVirus package realtime monitor feature

Users may experience performance problems when using Norton AntiVirus package realtime monitor feature.

FIX:
The performance slowdown is caused by the realtime antivirus monitoring engine. Please exclude *.bpd, *.bpf and *.bpfconfig file extenstions from Norton Antivirus virus checking rules.

This problem may affect other antivirus software packages.

SQL Diagrams.
This application gives you a graphical overview of your SQL Server database solution, it visualizes all relationships between all database objects. .

Read more

DB tools recommendations.
Where is a requirement, there also is a tool that meets that requirement. Let us find you a perfect tool!

Read more

Database Solutions.
If you have a problem or you are in a need of a cost-effective IT solution for your business, we are here to help.

Read more