Use an OUTPUT clause.

John

You can use LOGINPROPERTY(name, 'IsMustChange') to check whether the password has to be changed.

Please, please, please, though.... take an afternoon (or however long it takes) to read...

Edvard

Not easy to visualise without sample data, but do you just need to do a LEFT JOIN and add B.personalid IS NULL to your WHERE clause?

John

Satish

Yes, that's possible.  Please start by reading about log shipping and database mirroring.  You might also consider upgrading to a more recent version in order to take advantage...

http://www.sqlservercentral.com/blogs/spaghettidba/2015/04/24/how-to-post-a-t-sql-question-on-a-public-forum/

Do the values in ORDERDATE have a time portion?  If so, that'll explain the discrepancy, since in the ORDERDATESTRING column, you chop that portion off.

103 is dd/mm/yyyy, which is an ambiguous date format.  Could it be that your report server is set up to interpret dates as mm/dd/yyyy?

John

Please see this article about execution plans - or make your own investigations.  There's a lot of stuff out there.  The article is specifically about SQL Server execution...

There's no cost in making your code look readable, just as there's no cost in writing in paragraphs instead of one long sentence. Laying out your code will become second...

What error are you getting?  It might be easier to import the raw dates into a staging table and convert them from there.

John

You're not partitioning by j - you're doing the rank over the whole data set, so just remove the PARTITION BY clause and you'll get the desired result.

John

Dominik

You don't have to back up to a local drive - you can back up to a network share, thus rendering the copy step unnecessary.  Even if you...

I'm afraid I don't understand.  Here's a guess, though: alter your function like this:

ALTER FUNCTION [dbo].[test] (@input nvarchar(max))
RETURNS VARCHAR(250)
AS BEGIN
DECLARE @check1 nvarchar(max),
@check2...

Dominik

My advice is to use backup and restore.  It'll be a lot quicker for a big database and it's not susceptible to the issues you're seeing here.  Don't...

Such unpredictability is one of the reasons why I avoid the GUI where possible. But maybe there is logic to it.  A copy-only full backup doesn't have any effect on...