In MSDE 2000 no action can be performed on a database while it's attached andor when the service is running but in Express 2005 there are no such protections. The file can be copied, renamed, deleted all while the database is attached and the service is running. Is there a way to make Express act like MSDE 2000 in reguard to accessing the active files?
Thanks,
My database was overwritten by a new blank database,Is there a way i can recover my data coz all can find is a temp.mdf with some code and there I can see some of my data if i open it using notepad.I donn't have any backups.Is there a way that temp file can help?I've tried some data recovery but it didn't help.
Thanks
I have a two SQL 2012 databases in Development Environment as below:
1. LT_MSCRM (Main Development Database; Same database name is used across Testing and Live servers)
2. LTTEST_MSCRM (Just Created to practice something)
I have take the database back of LT_MSCRM from Testing server and want to restore it on LTTEST_MSCRM in Dev. Its failing because of the following error.
System.Data.SqlClient.SqlError: The file 'C:Program FilesMicrosoft SQL ServerMSSQL11.MSSQLSERVERMSSQLDATALT_MSCRM.mdf' cannot be overwritten. It is being used by database 'LT_MSCRM'. (Microsoft.SqlServer.SmoExtended)
Hello,
I've been working on an application that uploads an RDL to Reporting Services programmatically. I'm having problem with the data source properties for my uploaded report. The datasource for my report is custom datasource. It work s fine if the report still did not exist. But if the report already exist, after I upload the report to Reporting Services, the function will overwrite the RDL but it did not overwrite the Data source type correctly. Other setting like connection string is overwritten correctly.
For example, I already have RDL ABC with Data source type SQL, when I try to overwrite the existing RDL ABC which have Data source type Assembly, it still hold the SQL value for the data source type. But in the RDL itself (I checked in the rdl script in <DataProvider> tag), the value already overwritten to Assembly.
This problem also happen when I try to upload RDL using Report Manager. The Data source type are not overwritten by the action.
What should I do? Why it did not overwrite the datasource type? Maybe I do anything wrong here. I dont know what. Hope someone can help.
Thanks in advance
I'm trying to find a way to maintain the data that was UPDATEd in a table from being overwritten.
I used UPDATE in a table to include missing data. However, since I do not have access to the original table from where the data is derived, when I run my query, it knocks out the data in my table that was updated, because it is linked to the orginal table that has the blank fields. A few users do not have an employee email, and this has to be updated with a personal email account for now.
My update works fine, but is there a way I can use the statement in my query so that it updates each time it is run to maintain the user email address? This will solve the problem of not having to change the original table that I do not have access to.
if exists (select * test..dbo.Employee)
truncate TABLE
test.. dbo.Employee
insert into test.. dbo.Employee (EmployeeNumber
, EmplUsername
[Code] ....
Can't get over this error, and net searches reveal other postings similiar, but no answers.
SSIS database transfer task (with overwrite) from SQL 2k source to SQL 2k5 destination fails with:
Error: The Execute method on the task returned error code 0x80131500 (ERROR : errorCode=-1073548784 description=Executing the query "CREATE ROLE [RFRSH_USER] " failed with the following error: "User, group, or role 'RFRSH_USER' already exists in the current database.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly. helpFile= helpContext=0 idofInterfaceWithError={8BDFE893-E9D8-4D23-9739-DA807BCDC2AC}). The Execute method must succeed, and indicate the result using an "out" parameter.
The error seems the same regardless if the destination DB exists or not!
Anyone have a solution?