Create Windows Desktop widget which connects to SQL Server - sql

I want to create a desktop widget for Windows 7.
My requirements are below
I can provide SQL Server login credentials
It should connect to SQL Server
List out all the jobs in the server
Can anyone guide me on how to do this and where to start from?

Perhaps create a middle layer, that returns XML/JSON/HTML/..., that your widget can call through HTTP?
SQL Server 2005 supported native XML web services using SOAP/HTTP endpoints.
It's been deprecated in sql server 2008.
Your best bet would be to create a small HTTP server that acts as a broker between your SQL Server and desktop widgets.
You can find C# example code for HTTP server on Google.
http://www.google.is/search?hl=is&q=c%23+simple+http+server
Then let your widget just call the HTTP server for the information you want to display.
PS: Make your HTTP server log on and talk to the SQL Server, don't send database credentials (or ay other for that matter) over HTTP.

Related

Universal store app getting data from server

I want to build an app that gets data from a server and it displays it in xaml. I'm new to universal programs and in windows store apps in general. I haven't found anything useful yet as ms sql solutions require libraries that is not allowed for universal store apps :(
P.S.: The answer in how to connect sql server 2008 R2 with windows store application did not answer my question, but Jeffery's answer did.
You can’t connect to a MS SQL Server directly from the Windows App. The common way is host a data service and the app query the data through the REST API.
App -> data service (e.g. OData service) -> database (e.g. MS SQL Server)
In this case, you can deploy the SQL Server Data Service on IIS.
How to: Deploying OData Services using IIS & SQL Server
Then you use the HttpClient to retrieve the data from service.
Similar Question:
Windows phone 8.1 app connect with a database

SQL Server Browser - Startup Type - Best Practice

During the installation of SQL Server Express 2012 on a new machine, I am able to specify the startup type of both the SQL Server Database Engine and the SQL Server Browser.
By default, the SQL Server Database Engine has a Startup Type specified as Automatic.
SQL Server Browser has a default Startup Type of Disabled.
After reading about what function SQL Server Browser serves, it would seem that it is something you would want to have running all the time, since it essentially keeps tabs on the various DB instances, and seems like it would speed up development for example.
What are the pros and cons to setting the Startup Type of the SQL Server Browser to Automatic for example? Or to get any use, would you need to set it to Manual and then specify it launch at startup?
Thanks.
From my experience (after making direct access to SQL Server) SQL Server Browser useful if you have Named instances and\or nonstandard(standard is 1433)\dynamic TCP ports.
SQL Server Browser actually listens on UDP port 1434 (default, should be open in firewall) and returns Server\Instance name to IP address\port. If you want to connect from remote client to some MyServer\MSSQL2008 or get available in your network SQL Server Browser will return list of "Instance name\IP address\Port" to your client.

Do I need SSL Certificate for SQL Server and Web Server?

I am currently developing a website in C#, It requires to send requests to remote SQL Server.
I need to encrypt any communications from the client to the web server and to the SQL Server.
The SQL Server is currently used locally by another windows application, so the SQL server is being used locally and remotely.
So my concern is do I need to install cert for both servers ? If so will there be any connection problem between windows application and sql server ?
Thanks
you would only need a certificate on your sql server
use the encypt=yes option in your connection string on the web server.

Using Service Broker with Sql Server Express 2008

Is it possible to use external activation on sql express without going thru sql enterprise/standard?
I would like to send a message to sql express service broker, then have it notify my external application service running on the same box, in order to kick off a console app to pickup the message and process it. I do this already successfully from a remote Sql Enterprise db.
But now I need everything self contained on one box with Sql express, without using the remote Sql Enterprise.
However sql express has limitations so I'm wondering if I can use sql express as described in a stand alone configuration, without going thru Sql Enterprise. Thanks for your help!
You can do that, as long as the box sending the message is non-express edition.
The edition-related limitation of Service Broker is that a message must go through at least one non-express instance on its way from the sending service to the receiving service. There are no limitations on the External Activator service itself.

Reporting Services running on SQL Server 2008 Express

I know I can run Reporting Services on SQL Server Express w/ Advanced Services. The articles I have read do not touch on my question. I'm wondering, in this scenario, can remote users execute reports from the report server remotely using URL access ex:)http://mySQLExpressBox/ReportServer/rptMyReport....... etc - Or will reports only be served if the request comes from the same box/server?
This is possible -- it works the same way non-express editions work. Were you running into any specific issues when you attempted to do this?
The restriction that ewall was referring to is not a restriction on remotely executed reports, but on remote data sources. The Express edition is limited to local data sources (although you can get around this with Linked Servers). Ex: ClientA can remotely execute http://mySQLExpressBox/ReportServer/rptMyReport but mySQLExpressBox can only retrieve the data for the report from itself.