I've been having SQL 2000 startup issues for a while now and upon checking the logs, noticed a bunch of messages about analysis of the database at % completion and recovery complete. Then I see messages about it shutting down and starting back up again. Is this what is causing the problem? What is going on?
I have done installing sql server cluster 2014 and i want to add Analysis Service to current instance and i am getting error telling me this is clustered instance and you cant complete the installation .
We have a requirement to build SQL environment which will give us local high availability and disaster recovery to second site. We have two sites- Site A & Site B. We are planning to have two nodes at Site A and 2 nodes at Site B. All four nodes will be part of same Windows failover cluster. We will build two SQL Cluster, InstanceA will be clustered between the nodes at Site A Server and InstanceB will be clustered between the nodes at Site B, we will enable Always On Between the InstanceA and InstanceB and will be primary owner where data will be written on InstanceA and will be replicated to InstaceB. URL....Now we want we will have instanceC on the Site B and data will be writen from the application available on Site B, will be replicated to the instance on the Site A as replica.
Pages on a full recovery model database corrupted, need to ensure data loss is minimal for restore operation am thinking about restoring the latest full backup.
in the process of migrating a big db from server 1 to server 2, we had to roll back the change. I started with taking a full db backup and restoring it on server 2 with norecovery, and then a couple logs with norecovery, and then the last log with recovery.
Is there some way to continue this chain now, I mean to change the db to norecovery, or other way to restore logs.
I dont want to do a new full backup.
If I try to do a log restore now i get the message:
Msg 3117, Level 16, State 4, Line 1
The log or differential backup cannot be restored because no files are ready to rollforward.
We have 3 replica AG setup. 2 replicas are in sync/automatic failover, the other(DR Server, different subnet) in asynchronous/manual mode…All these replicas were on sql server 2012, Recently we upgraded DR server to 2014. Since then we have a problem, the AG databases in 2014 instance went into ‘Synchronizing/ in recovery’ state…The SQL server error log has message, the recovery couldn’t start for the database ‘XYZ’…We tried to create a new database and add it to AG , it works for fine for other two 2012 replicas, but on 2014 we see the same issue
We have an issue with a 3 node SQL 2012 Always on availability group. Normal operation is node 1 (primary replica) with node 2 and node 3 as secondary replicas.After some patching, SQL wasn't running on node 1 hence the AG flipped over to node 2. This went unnoticed for some time and the transaction log for one of the AG databases became full on node 2 and node 3. (I think this is because it couldn't commit the transactions on node 1 so couldn't truncate it's t-log?) The DB is using synchronous replication btw.So I started SQL on node 1 and flipped the AG back to node 1 (with a data loss warning but I accepted this).Now the issue is that on node 2 and 3, the DB in question is stuck in a "Reverting / In Recovery" State. I've tried various commands such as ALTER DATABASE SET ONLINE, RESTORE DATABASE WITH RECOVERY etc but these fail stating unable to obtain a lock on the DB.
The weird thing is that on node 1 the state of the DB is "synchronised".how to resolve this issue on node 2 and 3? I've left them overnight (in case they were rolling back transactions, the DB is fairly large) but nothing seems to have happened. remove the DB from the AG in node 2 and 3 and add it back in again, ie recreate the replication?
If you are doing a disaster recovery of an entire SQL 2005 cluster, can you just install SQL server and restore the system database to get the configuration?
I have, a SSAS 2012 tabular instance with SP2, there is a database on the instance with a read role with everyone assigned permissions. When configuring the Power BI analysis services connector, at the point where you enter Friendly Name, Description and Friendly error message, when you click next I receive the error "The remote server returned an error (403)." I've tested connecting to the database from Excel on a desktop and connect fine.I don't use a "onmicrosoft" account so don't have that problem to deal with.
We use Power BI Pro with our Office 365. As far as I can tell that part is working ok as I pass that stage of the configuration with a message saying connected to Power BI.The connector is installed on the same server as tabular services, its a Win2012 Standard server. The tabular instance is running a domain account that is the admin account for the instance (this is a dev environment) that account is what I've used in the connector configuration. It's also a local admin account. There is no gateway installed on the server.
I have a cube that we are processing nightly via an Analysis Service Processing Task in SSIS. In order to increase the performance of the processing time, we elected to use a lot of rigid dimension attributes, and do a full process of everything in the SSIS task. The issue that I am having is that after that task completes, I need to go into Visual Studio to deploy the cube becuase we are unable to browse or use the cube. This issue seemed to start once we changed the SSIS Analysis Service Processing Task to do a full process on the dimensions, rather than an incremental.
I would expect that once development is done, and it is processed and deployed, that is it. My thinking is that the SSIS task should just update the already deployed cube,
How to right choose key column in"Mining Structure" for Microsoft Analysis Services?
I have table:
"Incoming goods"
Create table Income ( ID int not null identity(1, 1) [Date] datetime not null, GoodID int not null, PriceDeliver decimal(18, 2) not null, PriceSalse decimal(18, 2) not null, CONSTRAINT PK_ Income PRIMARY KEY CLUSTERED (ID), CONSTRAINT FK_IncomeGood foreign key (GoodID) references dbo.Goods ( ID ) )
I'm trying to build a relationship(regression) between “Price Sale” from Good and “Price Deliver”.But I do not know what column better choose as “key column”: ID or GoodID ?
I am connecting to SSAS cube from Excel and I have date dimension with 4 fields (I have others but I don't use it for this case). I created 4 fields in order to test all possible scenarios that I could think of:
DateKey: - Type: System.Integer - Value: yyyyMMdd Date: - Type: System.DateTime DateStr0: - Type: System.String - Value: dd/MM/yyyy (note: I am not using US culture) - Example: 01/11/2015 DateStr1: - Type: System.String - Value: %d/%M/yyyy (note: I am not using US culture) - Example: 1/11/2015
Filtering on date is working fine:
Initially, in excel, filtering on date was not working. But after changing dimensional type to time, and setting DataType to Date, as mentioned in [URL] filter is working fine as you can see in the picture.Grouping on date is not working:
I have hierarchy in my Date dimension and I can group based on hierarchy, no problem. But user is used to pre-build grouping function of excel, and he wants to use that. Pre-build functions of Excel, Group and ungroup seems to be available as you can see in following picture:
But when user clicks 'Group', excel groups it as if it is a string, and that is the problem. User wants to group using pre-build grouping function available in Pivot table. I also find out that Power Pivot Table does not support this excel grouping functionality. And if I understood well, this pre-build grouping functionality of excel, needs to do calculation at run time, and that is not viable solution if you have millions of rows. So Power pivot table does not support pre-build grouping functionality of excel and hence we need to use dimension hierarchy to do the grouping. But I am not using Power Pivot table, I am using simple Pivot Table. So I expect grouping functionality to be working fine. Then I tried to do simple test. I created a simple data source in excel itself. And use it as source of my Pivot table. Then grouping is working fine. The only difference that I can see is (When double click the Measure value in Excel),For date values of my simple test, excel consider them as 'Date'.
For date values of my data coming from cube, excel consider them as 'General'
2.1. But value here is same as it was in simple test.
2.2. 'Date Filter' works just fine.
2.3. If I just select this cell and unselect it, then excel change type to 'Date' though for that cell.
2.4. I have created 4 different types of fields in my date dimension thinking that values of attribute of my dimension might be the problem, but excel consider 'General' for all of them.
2.5 This value (that can be seen when double clicking on measure) comes from 'Name Column' of the attribute. And the DataType defined is WChar. And I thought that might be the reason of issue. And I changed it to 'Date'. But SSAS does not allow it to change to 'Date' giving error : The 'Date' data type is not allowed for the 'NameColumn' property; 'WChar' should be used.
So, I don't know, what is the puzzle piece that I am missing.
1. Date filter works, group does not work
2. Excel consider it as 'General' string.
3. SSAS does not allow to change 'NameColumn' to Date.
I would like to know the best practice for running analysis service in terms of port usage. Is it better to run on a specific port or have dynamic ports ? We have clustered servers that run default on 2383 but not sure with non clustered what's the best way to get performance.
I have some questions about SQL Servers 2000 and 2005 compatibility. In my configuration I have to use both servers. The cubes are stocked in 2005 server. May I transfer from 2005 to 2000 Analysis Services the cubes?
If yes, what is the procedure? The result of migration is the same in the two different versions?
Windows Server 2003 SE SQL 2000 w/ 4 Veritas Netbackup 5.1 w/ MP5 (for backup/recovery)
Sometimes, not always, when I attempt to recovery a database I will follow the process of restoring the DB and it will complete with a status of successful. However when I attempt to view the DB in Enterprise Manager it states (loading) next to the DB - and never finishes.
As I said, this doesn't happen all the time, but of course when it happens I only know to start over, rebuild everything and go through the recovery process again. I am sure this is something simple.
I apologize for my lack of knowledge in regards to SQL.
I have removed a SQL Server 2000 installation, as need to re-install the OS also backed up the whole "Microsoft SQL Server 2000" folder that contains all the MDF and LDF files of the DBs.
Now i also had some DTS packages there but now when i have re-installed the whole setup; i could not get the DTS packages. Is there anyway to recover the DTS as i have the whole folder that contains the SQL Server information. DBs are attached again but only the DTS are left. There must be some place where SQL Server stores this information.
Can anyone please help me out as its so urgent for my work.
After a crash while running a query, the database now has (In Recovery) next to its name and is totally unaccessible. How long does this is last? Is there something I should do about it or do I just wait?
hi.. how do i create a log entries with checkpoint for each transaction when accessing and updating the database? i want to recover the data if in case of emergency....
also how do i check whether it has emergency during my project testing? haha.. i got an idea of switching of the electricity.. hahaha how should i do actually?
I have a problem. I am trying to set up a disaster recovery plan and have ran into some problems. Just so you are aware, we have tried setting up replication but it failed since the database does not have primary keys(don't ask--I have no control) and we have tried to set up log shipping but we do not have the Enterprise version of SQL server so that won't work. The database is over 200GB so shipping by tape or transferring full backups across the wire is impractical. So basically my question is - "What other options can we explore for setting up disaster recovery that do not involve 'substantial' expenditures?"
There is a direct connection set up between the off site data store.
Hi, I have SQL 7.0, SP2 running on NT 4.0 with SP5. I have a central publisher and numerous subscribers using nightly merge push replication. There seems to be some problem with the rollback after a failed attempt at replication. The publisher states that there was no response from the sub database and that it was suspect. From the sql logs on the sub, I can see that the db went into recovery mode, recovered 100%, howerver all the data in the subscribing database has disappered. The schema of all the tables is intact and the database still reads at its old size ~2Gigs. I can't see the data though. The publisher or other subscribers have suffered no similar loss of data. It seems that there was some sort of error when the database was trying to rollback to where it was before the attempted replication. Has anyone experienced anythng similar? Anyone know how I can recover the data?
I ran a dbcc checkdb, but it reported no errors, saying that there were no rows in any of my replicated tables.
Hey all, Is there any that i can bypass the recovering of a particular database when the server reboots? We are rebooting a prod. server and we need to bypass the recovery of a particular database as it is recovering forever. please help me out and i am gathering the information from web as much as i can to get an idea.
Hi, A test server I was developing on has died and all of my good work was on it. However I have a copy of the Data folder containing the folloing files:
Test_Data.MDF
Test_Log.LDF
Is it possible to restore my database from these files? If so how would I go about it?
Running SQL version 7 on "Terminal" Server I have a database marked in Load Receovery and we are unable to get to it. We tried MS SQL document on how to but we are still unable to recover it!
When I try to restore a database on one server from another server, by choosing the From device option, I am not able to see any mapped drives. So I always have to copy the backup file to my local drive before performing the restore. Is there any other way to do it? For example, Server1 contains a database db1. A full backup, differential backup and log backups of db1 are stored in , D:mssql7ackupfulldb1_full.bak D:mssql7ackupdiffdb1_diff.bak D:mssql7ackuplogdb1_log.bak The backup devices have been created using sp_addumpdevice. Server2 contains a database db1. If I need to restore a copy of db1 on server1 onto db1 of server2, I first copy D:mssql7ackupfulldb1_full.bak D:mssql7ackupdiffdb1_diff.bak D:mssql7ackuplogdb1_log.bak to a local drive on server2. I then restore using the from device option. SQL Server uses NT Domain account with admin. Privileges, log on as a service rt. Etc.
When I try to restore a database on one server from another server, by choosing the From device option, I am not able to see any mapped drives. So I always have to copy the backup file to my local drive before performing the restore. Is there any other way to do it using Enterprise Manager? For example, Server1 contains a database db1. A full backup, differential backup and log backups of db1 are stored in , D:mssql7ackupfulldb1_full.bak D:mssql7ackupdiffdb1_diff.bak D:mssql7ackuplogdb1_log.bak The backup devices have been created using sp_addumpdevice. Server2 contains a database db1. If I need to restore a copy of db1 on server1 onto db1 of server2, I first copy D:mssql7ackupfulldb1_full.bak D:mssql7ackupdiffdb1_diff.bak D:mssql7ackuplogdb1_log.bak to a local drive on server2. I then restore using the from device option. SQL Server uses NT Domain account with admin. Privileges, log on as a service rt. Etc.
1. I want some help regarding sql server 7.0.I had taken database backup (complete).And tried to restore in another machine. It restored successfully. But it does not create any logins/users. But it has some objects owned by user A If i create login as A and assigning default database, it is giving error and saying the user/role is already existing. Before restoring also i created login and after restoring I tried to assign the default database, but failed. I chaged the objects owner and tried again, still it is saying the user/role is existing. Can you suggest the solution.
2. I had backup of a database of SQL server 6.5. If i tried to restore on SQL Server 6.5/7.0, it is giving error, and saying it is not valid file. Any solution
I submitted an update query on a table of 80 million rows, in the weekend. When I returned on Monday, the transaction was still running. I thought some thing wrong happened and cancelled the transaction. It was taking long time to rollback the transaction. I recycled the SQL Server assuming it will do faster recovery. Now I realised that anyway it is going to take lot of time. And SQL server is not going to be up till the database is recoverd completely. Now can any body suggest me any thing to faster this process or skip this process. I dont know how long it is going to take rollback the transaction which ran for more than 70 hours.