I'm trying to create a simple Add-On for SQL Server 2008; it is simply going to pass a parameter from SQL 2008 to a console application.
Although Add-Ons are not specifically supported, according to these articles (1, 2), it is possible in 2005 and I'm assuming also in 2008. However, I've fallen almost at the first hurdle; I can't seem to find SQLWB.EXE (SQL WorkBench) in the expected place. I'm assuming that this file has been replaced in 2008, but I can't seem to pin down the equivalent version.
Has anyone any experience in general in developing 2008 Add-ons? Any good resources?
And can anyone indicate the 2008 replacement for SQLWB.EXE?
Sql Server Management Studio:
C:\Program Files\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\Ssms.exe
Related
How can we debug stored procedures in SQL Server 2018? As SQL Server 2018 and above versions do not have this option. Debugging makes life really easy. I have been trying to solve one problem for past one hour and if I could debug my stored procedure, I could have definitely save a lot of time. I did search a lot and did not find anything useful that could work.
Please do let me know if there is any way. Thanks.
How can we debug stored procedures in SQL Server 2018?
There is no such product as "SQL Server 2018" - I assume you're referring to one of the following:
SQL Server 2017
SQL Server 2019
SQL Server Management Studio 18
If you're referring to SQL Server 2017 or SQL Server 2019 then you can debug Stored Procedures by either:
Using SQL Server Management Studio 17.
Which may not work when connecting to a SQL Server 2019 instance, so YMMV.
Using SQL Server Data Tools (aka SSDT).
This is currently the officially supported tool for debugging SQL Server procedures and other objects in SQL Server.
SSDT is included in the free-as-in-beer Community Edition of Visual Studio without restrictions on its use in commercial settings.
But SSDT is not in any way a replacement for SSMS: SSDT only has basic tools for administering running SQL Server instances. So you'll need both SSMS and SSDT installed side-by-side.
If you're actually referring to SQL Server Management Studio 18 then you cannot debug procedures in SSMS 18 because Microsoft removed the feature for reasons unknown - I suspect perhaps involving the usual vague business reasons the veeps hand-wave with - because I cannot fathom any seriously good reason (though I agree the tooling was clunky, it did work at least).
To debug a procedure with SSDT you need to install Visual Studio (2017, 2019, they all have it) and select SSDT during VS installation. In previous releases of VS (like 2012, 2013, and 2015) SSDT used to be a separate download for VS but since VS 2017 it's part of the main installer.
When VS opens, dismiss the Start Screen and get to the main window, and go View > SQL Server Object Explorer, then connect to your server and the rest should be familiar to you.
As it sounds like you already have a substantial database project that exists in an extant SQL Server instance but also that you are not currently using SSDT - so I recommend you take this opportunity to actually move your project out of SQL Server and into an SSDT *.sqlproj - that way you can manage your database's design with source-control (Git, etc) and do local "builds" of your database (which will verify your code is valid T-SQL, it's saved me a lot of stress and trouble since I started using SSDT over 12 years ago) - it also makes publishing, deployments and schema changes a breeze (except for the fact the SSDT seems to get buggier and develops new glitches with each new release, ugh).
We currently work with all versions of SQL Server from 2005 onwards. To save time I try to do everything in a single version of Management Studio. This also helps if running newer client operating systems like Windows 10 which old client tools aren't compatible with.
Specifically when trying to view the graphical SSMS interface for index properties I get the following error if connected to a SQL Server 2005 instance.
In Object Explorer:
Database > Table > Indexes > Right Click > Properties
Full error text:
TITLE: Microsoft SQL Server Management Studio
Exception has been thrown by the target of an invocation. (mscorlib)
ADDITIONAL INFORMATION:
Cannot read property IsSparse. This property is not available on SQL Server 2005. (Microsoft.SqlServer.Smo)
This also happens in SSMS 2014, but not SSMS 2012.
So my question is; can something be done to work around this issue allowing one version of management studio to be used for all versions of SQL Server from 2005 onwards?
I'm guessing now, but as it works in SSMS 2012 there must be something going on that targets an older version of mscorlib. Maybe because SSMS 2012 uses a VS2010 shell and different .Net framework?
Many thanks in advance for your time.
There is an Active feedback about that on Microsoft Connect here. Someone suggest a workaround to go into Table Design and go to menu "Indexes/Keys...". It works, but some properties are not editable that way, like Included Columns. The other options left are to use SSMS 2005-2012 or use T-SQL script, like Aaron said.
This Snapshot is the info of SQL Server Management Studio which am currently running.
as you can see its of version 10.50.1600.1
Now when i try to backup a file the below error i get.
So it states that i am having a lower version.
Can you please advice?
Do i have to update? If yes, then how?
Error Snapshot
can you guys please help.
Thanks
Se we have t o explain to a programmer the difference between the management studio and the sql server? THe server does not care what version of management studio you run.
In case you do not know it, all you do when you do a backup is send a SQL command to the server. Management studio does nothing regaring the actual restore.
Check your SQL Server versions and upgrade them to at least 10.50.1600 - which would indicate a 2008 R2 version. You currently run 10.00.2531, which indicates 2008 Sp1.
Btw., all builds are here:
http://sqlserverbuilds.blogspot.com/
And, btw., not applying service packs to a database is gross neglect. There are someimtes interesting issues (queries not working) and you seem to have a habit of never patching your system - both, your management studio as well as your server are service packs behind the current patching level.
Can you please try generating Script with 'Schema and Data' option and executing that on your destination server.
Is it possible to write a plugin or a form for SQL Server Enterprise Manager version 8? I'm doing some simple queries all the time to admin the databases. So wondering if I could write something for it.
You mean the old SQL Server 2000 Enterprise Manager?? I don't think that old clunker had any extensibility points, sorry....
SQL Server Management Studio (SQL Server 2005 and newer) is based on Visual Studio and thus does have some extensibility - but it appears to be somewhat of a black art to write such a plugin - very little information is available.
Some is here:
The Black Art of Writing a SQL Server Management Studio Add-In
Building a SQL Server Management Studio Add-In
Extend Functionality in SQL Server 2005 Management Studio with Add-ins
SSMS Scripter - Internals, part 2 - plugging in
Since I usually do all my work in a query window, I just use a bunch of custom written stored procedures that I made, passing in parameters as necessary. all of my redundant work is done this way.
Does anyone know of a tool similiar to RedGate's SQL Data Compare that works with Microsoft SQL Server Compact 3.5?
For me the following process worked:
Install SQL Server Compact Toolbox extension.
Run the "Script database schema and data" command on both databases
Use a diff tool on generated files to see the changes.
In the end I solved this problem by Exporting my 2 SQL Server Compact Databases to SQL Server Express 2005 (although 2008 would work) using Data Port Console.
I then compared them using Red Gate SQL Data Compare.
This solution works just fine for me.
Not sure, but you could also have a look at the Apex SQL tools - Apex SQL Diff and Apex SQL DataDiff. There website is here. They don't specifically mention SQL Server Compact - but I'm sure you could inquire with them.
Red-Gate and Apex are my #1 choices for any kind of SQL tools :-)
Marc
Have you tried SQL Compare from starinix? They say it supports SQL Server (All Editions) so that may include compact edition.
This software does work as I have used it (for Yukon). It's also freeware which saves worrying about licensing.