In the previous installment of our series covering the most relevant features of SQL Server 2005 Express Edition, we started an overview of Service Broker full dialog-level security. In this article, we will conclude this subject by describing the remaining prerequisites and a method to invoke a secure dialog.
2009-01-06
1,292 reads
In my previous article Scheduling Jobs in SQL Server Express we saw how to make simple job scheduling in SQL Server 2005 Express work. We limited the scheduling to one time or daily repeats. Sometimes this isn't enough. In this article we'll take a look at how to make a scheduling solution based on Service Broker worthy of the SQL Server Agent itself.
2008-12-09
2,872 reads
In the recent installments of our "SQL Server 2005 Express Edition" series we have been discussing mechanisms that facilitate authentication of distributed systems participating in Service Broker conversations. This article discusses use of digital certificates in encrypting their content on the transport level.
2008-12-01
2,512 reads
This installment of our series focuses on establishing, conducting, and terminating a sample Service Broker dialog in a distributed environment, leveraging previously established routes and dialog-level permission.
2008-10-21
1,729 reads
As we all know SQL Server 2005 Express is a very powerful free edition of SQL Server 2005. However it does not contain SQL Server Agent service. Because of this scheduling jobs is not possible. So if we want to do this we have to install a free or commercial 3rd party product. This usually isn't allowed due to the security policies of many hosting companies and thus presents a problem. Maybe we want to schedule daily backups, database reindexing, statistics updating, etc. This is why I wanted to have a solution based only on SQL Server 2005 Express and not dependent on the hosting company. And of course there is one based on our old friend the Service Broker.
2008-09-23
3,241 reads
In the latest articles of our series dedicated to SQL Server 2005 Express Edition, we have been discussing Service Broker. This article describes the initial setup of components required to demonstrate a distributed implementation, with initiator and target services residing on two separate computers.
2008-09-18
1,535 reads
Marcin Policht explains the interaction of the primary elements of Service Broker's asynchronous messaging framework and describes a process of setting up the database objects necessary to demonstrate their sample implementation (which will be the subject of our next article).
2008-08-07
1,930 reads
In the previous installment of our series, we presented a variety of reasons that might influence your decision to upgrade a full-fledged member of the SQL Server 2005 family. This article discusses the actual implementation of this process, pointing out additional factors that might affect its complexity.
2008-07-07
1,969 reads
2008-08-18 (first published: 2008-06-25)
1,750 reads
2008-04-24
3,372 reads
Creating a Fabric workspace takes about 30 seconds. Restructuring workspaces after people have built...
By Steve Jones
It’s a small change, but a handy one. Flyway Desktop (FWD) now includes the...
By Steve Jones
Software is hard. While I love our Lucid Gravity, I realize that they are...
Comments posted to this topic are about the item Adding new column with DEFAULT...
Comments posted to this topic are about the item Advanced Deployment Scenarios: Stairway to...
Comments posted to this topic are about the item You Need a DBA Pipeline
Which number did the two COUNT(*) return:
DROP TABLE IF EXISTS #tmp CREATE TABLE #tmp (id INT NOT NULL) INSERT INTO #tmp (id) SELECT gs.value FROM GENERATE_SERIES(1, 5) AS gs ALTER TABLE #tmp ADD my_value INT NOT NULL CONSTRAINT df_tmp_my_value DEFAULT 1 SELECT COUNT(*) FROM #tmp AS t WHERE my_value = 1 ALTER TABLE #tmp DROP CONSTRAINT df_tmp_my_value ALTER TABLE #tmp ADD CONSTRAINT df_tmp_my_value DEFAULT 2 FOR my_value SELECT COUNT(*) FROM #tmp AS t WHERE my_value = 1See possible answers