DB Backup - Single User Mode

Tx for your responses.
I completely understand and accept that there is no need to do a
backup in single user mode, but for one case if the server is already
in single user mode ..
Here is what I found, in SQL 2000 it was possible to do the
backups(in single user mode) while the SQL 2005 server fails to accept
the connection for backup (the same code/binary SQL-DMO statements are
used for both).
Are there any major changes between SQL server 2000 and SQL server
2005 ?
On Oct 31, 3:02 am, "Tibor Karaszi"
<tibor_please.no.email_kara...@.hotmail.nomail.com> wrote:[vbcol=seagreen]
> If you mean regular backups (usingBACKUPDATABASE andBACKUPLOG commands), then no, no need to set
> the database tosingleusermode...
> --
> Tibor Karaszi,SQLServer MVPhttp://www.karaszi.com/sqlserver/default.asphttp://sqlblog.com/blogs/tibor_karaszi
> "velu5" <thirumalaiv...@.gmail.com> wrote in message
> news:1193743910.012534.3610@.v29g2000prd.googlegrou ps.com...
>
What's New in SQL Server 2005:
http://www.microsoft.com/sql/prodinfo/overview/whats-new-in-sqlserver2005.mspx
http://technet.microsoft.com/tr-tr/library/ms170363(en-us).aspx
Ekrem nsoy
"velu5" <thirumalaivelu@.gmail.com> wrote in message
news:eb680ec9-d7c5-40c2-bec6-bbbdeada23af@.e23g2000prf.googlegroups.com...
> Tx for your responses.
> I completely understand and accept that there is no need to do a
> backup in single user mode, but for one case if the server is already
> in single user mode ..
> Here is what I found, in SQL 2000 it was possible to do the
> backups(in single user mode) while the SQL 2005 server fails to accept
> the connection for backup (the same code/binary SQL-DMO statements are
> used for both).
> Are there any major changes between SQL server 2000 and SQL server
> 2005 ?
>
> On Oct 31, 3:02 am, "Tibor Karaszi"
> <tibor_please.no.email_kara...@.hotmail.nomail.com> wrote:
>

datetime procedure argument wont accept datetime value?

I am using Microsoft SQL Server Management Studio to connect to MSSQL 2005.... There is a stored procedure which has the following value amongst its parameters:

@.created_after datetime = null,

When I right-click the procedure and select Execute Stored Procedure, and enter a date like "23/01/2007 8:54:59 AM" into that field the following error is produced:

Msg 8114, Level 16, State 5, Procedure search, Line 0
Error converting data type nvarchar to datetime.
(1 row(s) affected)

As well as showing the following:

USE [FileStore]
GO

DECLARE @.return_value int

EXEC @.return_value = [dbo].[search]
@.created_after = N'23/01/2007 8:54:59 AM'

SELECT 'Return Value' = @.return_value

GO

Any idea why it will not accept my date value?

Any help would be appreciated ... Thank you :)

try input the datetime in universal format YYYYMMDD HH:MM:SS

Your system date format might not be DD/MM/YYYY|||You seem to be 100% correct! How can I change this?

DateTime format in Report manager (parameter)

Hi,
I would like the report manager to accept datetime parameters in a specific
format (European). I've set the report settings to the correct language, and
parameter input in the visual studio report designer works like it should.
But after deploying the reports, the way the datetime parameter has to be
inputted changed from European (dd/mm/yyyy) to US format (mm/dd/yyyy). The
dates on the report itself are shown correctly.
Is there a way to tell the report manager which datetime format it should use?
thx!
--
AndreasThe date format will be based on the locale requested by the client browser.
--
Brian Welcker
Group Program Manager
SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Andreas" <Andreas@.discussions.microsoft.com> wrote in message
news:1A293983-0517-46C4-9A70-153B59DB47F3@.microsoft.com...
> Hi,
> I would like the report manager to accept datetime parameters in a
> specific
> format (European). I've set the report settings to the correct language,
> and
> parameter input in the visual studio report designer works like it should.
> But after deploying the reports, the way the datetime parameter has to be
> inputted changed from European (dd/mm/yyyy) to US format (mm/dd/yyyy). The
> dates on the report itself are shown correctly.
> Is there a way to tell the report manager which datetime format it should
> use?
> thx!
> --
> Andreas