Please read the following article: http://www.karaszi.com/SQLServer/info_dont_shrink.asp

You should not shrink the transaction log on a regular basis. And no, a database backup does not back up the transaction log. ...

Are you running on Vista? If so, are you trying to start the agent through SSMS? If yes, then you need to be running SSMS as an Administrator...

You should not shrink your database on a regular scheduled basis. You should always maintain enough free space in the database to allow for index rebuilds and reorgs -...

Hemalatha (10/17/2008)

---

Hi All

I know that this is a very simple query but somewhere struggling

These are the columns

gps_datetime registrationno, speed

10/10/2008 A123 ...

psangeetha (10/17/2008)

---

Jeff, that is a very good question. But thats how the application is been set up. Depending on the case_seq number, the description in the form_items appears on the...

psangeetha (10/17/2008)

---

Jeff, Thanks. The view gives me the output of the select query.

create view test (case_seq,description,case_cred,number)

as SELECT b.case_seq,a.description

,a.case_cred

...

psangeetha (10/17/2008)

---

Jeff,

To create a view to generate the case_seq from the form_items table like below:

create view caseseq (case_seq)

as

select b.case_seq from form_items a,case_form b where

b.case_name='test' and a.case_cred=b.case_cred order by...

Are you sure you really need to store that information? If not, you can return that information using row_number() in the query (or create a view) that would generate...

Seth, you are right - I missed that 'small' little detail 😉

CREATE PROCEDURE [dbo].[svg_RiskGetCardLocationByIso]

declare @CardNum varchar(100),

declare @DateFrom datetime,

declare @DateTo datetime,

@IsoNum int,

@CardNumDES3 varchar(100) ='0000000000000000',

@username varchar(100)=''

AS

...

Remove the word declare from the list of parameters. It is not valid at that point and...

Yes, the following code is the problem:

, (SELECT r.ResourceID

...

If you are using linked servers, make sure you have RPC enabled on the linked server and you can perform the following:

Execute serverb.databaseb.schemab.procedure;

Please review the following article and provide the relevant data so we can provide a tested and validated solution:

Best Practices: http://www.sqlservercentral.com/articles/Best+Practices/61537/

In the meantime, you could do something along the lines...

Here you go:

http://blogs.msdn.com/sqlserverstorageengine/archive/2007/03/22/easy-way-to-create-a-corrupt-database-for-testing.aspx

I run the integrity check nightly using the PHYSICAL_ONLY option, and weekly perform a full integrity check.