Viewing 14 posts - 1 through 14 (of 14 total)
Hi SSC Guru,
I haven't get any answers yet.Can you please help on this?
November 15, 2019 at 2:12 pm
Can't we restore the DB using "Tasks->Restore->Files and Filegroups" option? I was following below steps.
1) Created a new database
2) Navigate to Tasks->Restore->Files and Filegroups
3) In “General” tab,
a. I gave the...
September 24, 2019 at 9:58 am
Can you please explain the GUI box (caption) you are referring in second tab?
September 23, 2019 at 7:18 am
I'm able to achieve through below SQL Query. How do I do this in SQL Server Management Studio Wizard?
--Create TestDB1
CREATE DATABASE TestDB1;
GO
--Create TestDB2
CREATE DATABASE TestDB2;
GO
--Backup of TestDB1
BACKUP...
September 20, 2019 at 2:01 pm
No, I'm just passing arguments by using -v inputvar1="abc" inputvar2="xyz".
Here, user may pass argument called "inputvar3". If user fails to enter "inputvar3" then it's printing the message like 'inputvar3' scripting...
December 5, 2014 at 5:12 pm
Can anyone help me on this?
December 5, 2014 at 10:13 am
No, the files were not moved. I was re-attached the MDF & LDF files from the actual location. And I believe the permission of the files were not changed because...
August 21, 2009 at 5:01 am
Thanks for your reply.I have many databases in my server and all the DB MDF & LDF files pointed to the same drive (E:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\). If there was...
August 20, 2009 at 5:50 am
Everything fixed now using the MDF & LDF files.Is there any way to find what was happened before this db suspect?
Thx.
August 20, 2009 at 4:31 am
Database State:
----------------
I don't know the database state since I didn't check the database state before re-attaching the database.
Errors in Error log:
--------------------
I went ahead the erorr log and found the following...
August 19, 2009 at 12:16 pm
I was re-attached the database using their MDF file. I want to know the reason why this was happened? On what cause the problem?
Thx.
August 19, 2009 at 7:33 am
I have a Database trigger and it throws the above said message. Just now I updated the NOCOUNT value is ON and got the right message. Thanks for your earliest...
August 19, 2009 at 5:54 am
alter PROCEDURE test
AS
BEGIN
-- SET NOCOUNT ON added to prevent extra result sets from
-- interfering with SELECT statements.
SET NOCOUNT ON;
select 1
END
go
August 19, 2009 at 5:24 am
Viewing 14 posts - 1 through 14 (of 14 total)