Once a topic is created, other people may see it and have an interest in it.

For their sakes, rather than deleting a topic answered elsewhere (or editing out the original...

quote:

---

For a complete server swap I've always just backed up and restored the msdb database to retain the DTS packages and all...

Almost forgot - INSERTs most certainly can lock up the table when done in bulk, as can UPDATEs. Whether this is a problem for you or not depends on...

quote:

---

Bearing in mind that I am a new comer to SQL Server, can I ask some suupplementary questions to make sure I...

I believe that a query batch is treated as a single transaction.

For instance:

SELECT Fred FROM tblStatistics

DELETE tblstatistics

GO

should leave your table intact (assuming you don't have a...

With the given delete statement, that may be true, but it certainly isn't clear.

To my eye (and, I assume, the original posters), the following should happen:

Since there is no join...

I've thought about this sort of thing aften, but have never actually implemented it.

That said, here are my thoughts.

Your interface will be the mechanism for determining the structure of the...

Seems to me that the problem will lie in the user interface, not the stored proc.

I mean, if the user can indicate that they want:

firstname = 'David'

and (lastname = 'Johnson'

or...

One other possibility that does come to mind - some text editors will converts tabs to spaces. Unlikely to be the problem, but a possibility.

The problem is that nothing in your subqueries matches your counts to a specific location. One solution might be simply changing the alias on v_Site for the subqueries to,...

Actually, up until two months ago, all this data was on one server. We split user profile information off to another server to lighten the load and speed things...

To the best of my knowledge, SQL Server stores plain, ordinary text. Any deviations from such (bold, italics, etc.) has to be handled by the application displaying the text.

If...

Don't have your tables, so it'd be easier for you to check this out than me.

I'd try simply rewriting things as an inner join. For the first SQL statement...

You can use UDFs in the same places you can use built-in functions. For instance, I created:

CREATE FUNCTION myTime(@theDate datetime)

RETURNS varchar(30)

AS

BEGIN

RETURN REPLACE(CONVERT(varchar,@theDate,106),' ','-')

END

If I then execute:

select dbo.myTime(current_timestamp)

in...

I realize that, as this uses a cursor, it's the ultimate evil; however:

SELECT Timecard.EmpID,

SUM(Timecard.WrkHrs) AS WrkHrs,

WrkEmp.FName AS EmpFName,

WrkEmp.LName AS EmpLName,

MgrEmp.EmpID AS MgrID,

MgrEmp.FName AS MgrFName,

MgrEmp.LName AS MgrLName

INTO #EmpHoursByProject

FROM Timecard

INNER JOIN Project...