Viewing 15 posts - 421 through 435 (of 3,011 total)
Follow the ALTER DATABASE with a USE statement in the same batch will usually get the connection.
USE [master]
ALTER DATABASE [MyDatabase] SET SINGLE_USER WITH ROLLBACK IMMEDIATE;
USE [MyDatabase]
October 11, 2012 at 9:32 pm
Did you test it to verify that this syntax does not work?
WITH STATE = ON
October 11, 2012 at 9:00 pm
If having the database in read only mode is OK, you could restore the database into standby mode, and then apply transaction log backups to roll it forward each day.
October 11, 2012 at 9:48 am
nmaddox (10/11/2012)
October 11, 2012 at 9:35 am
You can add more detailed descriptions as extended properties via SSMS or with a stored procedure call:
EXEC sys.sp_addextendedproperty
@name=N'ColumnDescription',
@value=N'Credit Card Expiration Date' ,
@level0type=N'SCHEMA',
@level0name=N'dbo',
@level1type=N'TABLE',
@level1name=N'CustomerOrder',
@level2type=N'COLUMN',
@level2name=N'Order_CCExp'
October 11, 2012 at 9:25 am
TOP is required when you have an ORDER BY in a derived table or view.
October 10, 2012 at 2:06 pm
jbalbo (10/10/2012)
yes definitly datetime, double checked to make sure I haven't lost it.... lol
Just wondering, because different types of date/time data types have different display formats in SSMS.
declare @date date,
@datetime...
October 10, 2012 at 9:21 am
Resender (10/10/2012)
October 10, 2012 at 9:12 am
Resender (10/10/2012)
...you can do it in Oracle, but that is cause in Oracle a database is its own server...
I don't think that is true either.
Any true RDBMS does not allow...
October 10, 2012 at 8:44 am
Danzz (10/10/2012)
All my .bak backup cleanup history works fine, cleanups after 48Hrs.
I doesn't work for my txt file to cleanup. These txt file are created by job...
October 10, 2012 at 8:39 am
Resender (10/10/2012)
Both the database...
October 10, 2012 at 8:29 am
Is the "date/time field" you are updating actually a DATETIME data type?
What is the actual data type?
October 10, 2012 at 8:25 am
vick.ram79 (10/6/2012)
yup - the nolock is soo much faster...
I am not suggesting that you use NOLOCK in your stored procedure.
You should investigate why your query is being blocked. You...
October 6, 2012 at 1:44 am
You could create a unique index or constraint that has all eight columns to guarantee that you cannot have duplicates.
There can be a lot of overhead to such a wide...
October 6, 2012 at 1:38 am
Try running the statement below. If it runs much faster, your original query is probably being blocked.
select COUNT(*) from TransactionLog with (nolock)
October 5, 2012 at 10:50 pm
Viewing 15 posts - 421 through 435 (of 3,011 total)