Monday, April 1, 2013

[SQL Server 2008 issues] sql server readonly permission

[SQL Server 2008 issues] sql server readonly permission


sql server readonly permission

Posted: 31 Mar 2013 07:16 PM PDT

Which permission under sql server database properties->permission in SSMS should i select to make the database readonly for a user?

Transaction log in Subscriber database for Transactional Replication

Posted: 04 Mar 2013 08:31 AM PST

I have created replication between two SQL Server 2008R2 databases and it has been functioning well since the initial setup 3 months ago. The publisher database is the back-end for an OLTP application with 50 users who are working constantly, making changes and add new information. The Subscriber database is used for reporting. Today I noticed that the Subscriber database was set to Full Recovery Mode with no transaction log backups. I panicked for a minute and took a quick look at the Transaction Log drive on the Subscriber server - it has 50% free space, 24 GB. I was amazed that I had been avoiding what normally would cause a drive-full issue.My question is this. Since replication is constantly making changes to the Subscriber database (updating various tables as they change in the Publisher database), why is the Subscriber log file not filling up and giving me grief since I don't run backups on the Subscriber database - and haven't done for the entire three months this has been running? Gail Shaw mentioned in another forum question while I was researching this, that 'Replication does not in any way use the Subscriber's log file'. I'm not sure that I understand the seeming contradiction been the updating going on in the Subscriber database, Full Recovery mode, no Transaction Log backups taking place and the Transaction Log not filling up.Can anyone enlighten me and/or point me to articles that might help me understand this more thoroughly??Thank you. Willem

Publishing and accessing SQL Server 2008 Reports

Posted: 31 Mar 2013 12:20 PM PDT

I 'm new to SQL Server database and I need help. I 'm trying to publish sql reports for users to access from the web. We have SQL server 2008 database with data, and I have installed a separate SQL server 2008 with Reporting Services on my windows xp machine. I have created data source from the remote sql server 2008 installed on a Windows Server, and publish the reports. I can access the report manager through the URL (//localhost:8080/ReportServer) on my xp machine browser. However, when I typed the same URL from another computer, I get page cannot be displayed message. What is going on? Does the report manager URL needs to be configured on the SQL Server that has the database instance? Please help. ThanksTo make myself clear, what I 'm trying to acomplish is to create and publish reports for users to access from their workstations. Any help will be appreciated.

split fixed width row into multiple rows in SSIS

Posted: 31 Mar 2013 11:13 AM PDT

I Have a fixed width flat file and that needs to be loaded into multiple oracle tables(one row need to be splitted into multiple rows)the numbers which are on top of each column is there size,and my desired output should look like shown below. [code="sql"]Flatfile data(fixed width):3 6 3 11 3 10 3 10 3ID NAME AGE CTY1 ST1 CTY2 ST2 CTY3 ST3200JOHN 46 LOSANGELES CA HOUSTON TX CHARLOTTE NC 201TIMBER54 PHOENIX AZ CHICAGO IL 202DAVID 32 ATLANTA GA PORTLAND AZ [/code]the occurrence may vary.. it can grow upto 20-30[code="sql"]DESIRED OUTPUT:TABLE1ID NAME AGE200JOHN 46201TIMBER54202DAVID 32[/code][code="sql"]TABLE2ID SEQ CTY ST200 1 LOSANGELES CA 200 2 HOUSTON TX 200 3 CHARLOTTE NC201 1 PHOENIX AZ 201 2 CHICAGO IL 202 1 ATLANTA GA 202 2 PORTLAND AZ [/code]can some one help me outThanks

TRIM and Date Format question

Posted: 31 Mar 2013 05:25 AM PDT

I have tried using the TRIM function in the below query to remove a leading zero in the Department Code (vEPayrollBase.[PrbPayDept] AS [Department Code]). Does anyone know how what the correct language is? Also, how would I modify Date of Birth to format as mm/dd/yyyy instead of the default? ThanksSELECT vEPerson.[EpFirstName] AS [First Name], vEPerson.[EpMiddleName] AS [Middle Name], vEPerson.[EpLastName] AS [Last Name], vEPerson.[EpEmail] AS [E-mail address], vEJob.[EjTitle] AS [Job Title], vEbase.[EbClock] AS [Employee ID], vEPayrollBase.[PrbPayDiv] AS [Location Code], vEPayrollBase.[PrbPayDept] AS [Department Code], (CASE WHEN [EpCountry] = 'USA' THEN 'US' ELSE [EpCountry] END) AS [Country], (CASE WHEN [EeStatus] = 'Active' THEN 'A' ELSE [EeStatus] END) AS [Status Indicator], vEPerson.[EpDateBorn] AS [Date Of Birth], vEPerson.[EpSex] AS [Gender], vEPerson.[EpStreet1] AS [Home address], vEPerson.[EpStreet2] AS [Home address 2], vEPerson.[EpCity] AS [City], vEPerson.[EpState] AS [State], vEPerson.[EpZip] AS [Zip], vEPerson.[EpHomePhone] AS [Home Phone], vEJob.[EjWorkPhone] AS [Work Phone], vEPerson.[EpCellPhone] AS [Mobile Phone ], vEPayrollBase.[PrbDateOriginalHire] AS [Original Hire Date]FROM vEPerson INNER JOIN vEbase ON vEbase.[EbFlxID] = vEPerson.[EpFlxIDEb] INNER JOIN vEJob ON vEbase.[EbFlxID] = vEJob.[EjFlxIDEb] INNER JOIN vEPayrollBase ON vEbase.[EbFlxID] = vEPayrollBase.[PrbFlxIDEb] INNER JOIN vEEmploy ON vEbase.[EbFlxID] = vEEmploy.[EeFlxIDEb]WHERE (((((vEPerson.[EpDateBeg] <= '2020-06-20 23:59:59' AND (vEPerson.[EpDateEnd] >= '2020-06-20 00:00:00' OR vEPerson.[EpDateEnd] IS NULL))) AND (((vEJob.[EjDateBeg] <= '2020-06-20 23:59:59' AND (vEJob.[EjDateEnd] >= '2020-06-20 00:00:00' OR vEJob.[EjDateEnd] IS NULL)) AND vEJob.[EjPrimary] = 'P'))) AND (vEbase.[EbArchive] <> 'Y' AND vEbase.[EbFlagEmp] = 'Y')) AND (vEPayrollBase.[PrbDateBeg] <= '2020-06-20 23:59:59' AND (vEPayrollBase.[PrbDateEnd] >= '2020-06-20 00:00:00' OR vEPayrollBase.[PrbDateEnd] IS NULL)))AND (vEEmploy.[EeDateBeg] <= '2020-06-20 23:59:59' AND (vEEmploy.[EeDateEnd] >= '2020-06-20 00:00:00' OR vEEmploy.[EeDateEnd] IS NULL))

Newbie (Know-nothing-bie:) Needs Urgent Assistance with SQLExpress

Posted: 31 Mar 2013 02:28 AM PDT

I have very little experience with SQL other than using it. I am a hardware tech. But I do have some knowledge of when something isn't working right and not due to hardware.One of my oldest clients had a problem with a dead hard drive. Unfortunately, replacing the drive and reinstalling the OS was the least of their problems. They have a business that has gone through several downsizings and currently there are only 2 people who need to access a piece of software they use to schedule appointments. This is a very OLD piece of software they have used for years. The company who originally sold the program is also gone, none of the tech support or sales phone numbers connect. They must have sold the "name" of the software as I can find the place that now sells it but they offer no support for it in it's original form. The last time I was involved with it was about 4 years ago when they had to replace their Windows XP system which was used as a "peer to peer" server for the data files.I remember talking to a tech at the company on the phone who guided me through getting the MDF/LDF's off of XP and onto Windows 7. I also remember it was not easy but once done it worked as before. The current problem was due to a hard drive failure on the 4 year old Windows 7 system. They have many years' of backup files but it is only the "data" in a ".bak" format. They still have an installation program to create the client end. But I remember four years ago that creating the SQL instance was a "do it yourself" thing. I still have the original password used at the time but it is of little use. Every attempt I have made to link the database using the supplied "DB connect utility" fails.I am not sure if the problem is something I am doing or if I need to be using a different version of SQLEXPRESS. Or maybe some small thing I have missed. I have tried various versions of SQL 2008 (and even 2005 ). I thought about trying 2012 but after spending so much time getting nowhere, I think I need some advice about what I am doing wrongI anyone here can point me the right way I would appreciate it. Better yet, I wouldn't mind paying someone to provide remote support for the SQL installation. Without this program they are back to pen and paper and the quotes for a replacement program are not in their budget.

No comments:

Post a Comment

Search This Blog