Viewing 15 posts - 616 through 630 (of 641 total)
Jason, thank you.
Nothing better than dialogue to help make the documentation, even excellent documentation on msdn.microsoft.com come together.
I see I was missing the middle step. Using the instructions at...
June 21, 2010 at 10:33 pm
To answer the question "did I create a user in the database and associate it to a login?", my answer is that I did the following:
Expanded the default instance-> Security...
June 21, 2010 at 8:17 pm
I ran the same TSQL command against another db: AdventureworksLT and it worked! So, I retried against AdventureworksDW and it failed once again. I tried against a 3rd db:...
June 21, 2010 at 6:58 pm
I'm going to go with your first advise to begin with:
"Grant db_datareader to the specific databases that the user is permitted to see. "
When I run this:
use AdventureWorksDW
go
exec sp_addrolemember...
June 21, 2010 at 3:53 pm
Jason,
The above worked. Thanks.
At this point how to I restrict this user to only querying (reads) the databases on the instance?
June 21, 2010 at 12:11 pm
Hi Jason,
Aj jaj jaj!. Yes, I think I can find the user as an object in the dialog box afterall. Though the naming convention for the Name is slightly...
June 21, 2010 at 11:17 am
OK, thanks, paul.knibbs and GilaMonstor. Thank you for allowing me to whittle away at this big question, here.
So, on my own machine, where the instance that I am admin...
June 10, 2010 at 4:49 am
Paul, when would I choose to run SQL Server under a specific service account? Can you give me some examples why chosing one over another would benefit me (as the...
June 10, 2010 at 12:07 am
Hi. I started a new post with this question and it was answered really well there. Actually, I think it may have morphed into a better question by...
June 8, 2010 at 10:15 pm
OK, in my case I have all permissions as I am administrator.
But, I want to explore this a little further becuase I am having trouble understanding how to utilize service...
June 6, 2010 at 8:05 am
Jeffrey Williams-493691 (5/31/2010)
".... validate that the login running SQL Server has access to the directory and file where the backup file exists....."
Jeffrey, if you aren't totally sick of me....will you...
June 1, 2010 at 1:45 am
Thank you. this worked.
RESTORE DATABASE [AdventureWorksDW]
FROM DISK = N'G:\BU\AdventureWorksDW_May31_2010_FULL.bak'<--origin
WITH FILE = 1,
MOVE N'AdventureWorksDW_Data'<--logical name
TO N'C:\Program Files\Microsoft SQL <--destination
Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\AdventureWorksDW_Data.mdf',
NORECOVERY
GO
Problem was combination of syntax and flow.
I do spend time with...
June 1, 2010 at 1:11 am
USE AdventureWorksDW
GO
RESTORE FILELISTONLY
FROM DISK = N'G:\BU\AdventureWorksDW_May31_2010_FULL.bak'
The logical file name given for the data file is AdventureWorksDW_Data. I used this in the Restore WITH MOVE statement as follows....
May 31, 2010 at 11:04 pm
I am really floundering here.
I don't have any official backup_device. I just send my backups to my G:\BU folder.
When I run RESTORE FILELISTONLY FROM AdventureWorksDW_May31_2010_FULL I get...
May 31, 2010 at 9:56 pm
Hi Jeffrey, thanks.
I ran
Select * from sys.database_files.
i found a column called "physical_name" (none called "logical name") and used it. See below. Still error.
RESTORE DATABASE [AdventureWorksDW]
FROM DISK...
May 31, 2010 at 9:23 pm
Viewing 15 posts - 616 through 630 (of 641 total)