| bio | website | |
|---|---|---|
| location | ||
| age | ||
| visits | member for | 8 months |
| seen | Apr 17 at 15:10 | |
| stats | profile views | 10 |
|
Apr 4 |
comment |
RESTORE DATABASE is terminating abnormally My guess would be that a user or process has crept in and taken up that single user on the database and is then preventing the restore from happening. You would probably be better served setting the database offline and doing the restore. As others have suggested, remove the try/catch block to get the full error message, or get it from the Errorlog so that you have more information. |
|
Mar 12 |
comment |
Can the same database be log-shipping secondary and primary at the same time? You will not be able to setup transaction log backups on the secondary until the database has been recovered. I would recommend either scripting out your log shipping backup job and putting that in a disabled state on the secondary server, or just setup a regularly scheduled transaction log backup job on the secondary which you would just enable when you recover the database. |
|
Mar 6 |
comment |
Migration advice from SQL server 2000 bak The obvious answer would be Windows 2012 and SQL 2012, however you are going to be limited to SQL 2008/R2 given that you are trying to bring the database up from SQL 2000 (and that is assuming that the database does not utilize code features that were removed). If you are going to keep SQL with the file/print sharing services I recommend sticking with a server OS. 2008 might be the best way to go and then figure out a route for yourself to 2012. |
|
Feb 6 |
comment |
Does SQL Server care about the location of accounts in Active Directory? Do you mean where they reside within the OU structure? If that's the case then no, SQL doesn't care. |
|
Feb 6 |
comment |
Restore backup fails - not enough disk space OP asked how to bypass the disk space check. Just answering the question asked. Given the size listed (14GB) it won't restore to express anyway (10GB limit) |
|
Feb 6 |
comment |
Best way to defrag/compact a database for archival purposes How about two new filegroups, one for the LOB data. Create new tables with LOB on the second filegroup. Insert the data into the tables, drop the old, rename the new, shrink the primary. |
|
Feb 5 |
comment |
Best way to defrag/compact a database for archival purposes It's just a thought, but why not create a new filegroup, add a file, set a reasonable growth (say 500MB) and then rebuild your tables onto that new filegroup. Then shrink the primary file down to almost nothing. You won't care a lick about fragmentation on the system tables. |
|
Feb 5 |
comment |
Identify File Growth Events This is good information, just bear in mind that some of those events could well have expired from the default trace. |
|
Feb 4 |
comment |
SSRS appears to be ignoring Permissions set using Report Manager Out of interest, have you tried running IE as an admin? There are issues connecting locally with IE when it is not. |
|
Jan 24 |
comment |
Why can't I read my transaction log backup file using fn_dump_dblog? I have the same issue running 2008R2 10.50.4000. |
|
Jan 18 |
comment |
What are the advantages of a monitor server for log shipping You can absolutely do that. Realistically that's all the monitoring server does anyway. It doesn't provide you anything more than that. You can also use any existing server as the monitoring box, just so long as it is able to access both the primary and secondary(s) |
|
Jan 17 |
comment |
Read only/Standby database - Set user permissions If you want security you can go a step further and remove the login from the primary server (just leave the user intact). That way you have the user in the database but no login on the server, thus securing your primary. Create the login on the secondary (specifying the SID from the primary) and you'll have permisions on the secondary without granting access to the primary. |
|
Oct 26 |
comment |
SQL Server Concise List Of Trace Flags The vast majority of Trace Flags are undocumented as they should not be used. They are there for advanced troubleshooting purposes by the SQL support team only. The link you found is valid for known and supported trace flags. |
|
Oct 25 |
comment |
Post replication powershell script - on subscriber Transactional replication job execution is ongoing, but you can schedule the snapshot as often as you like. It will not actually take a snapshot if nothing has been reinitialized, but you still go through all the steps. |
|
Oct 25 |
comment |
Post replication powershell script - on subscriber Yes. Snapshot replication will execute and then stop, whereas transactional replication will not stop executing (as it will continue to apply transactions on the remote server). Or are you just refering to the you needing to run processes before and after the snapshot (or if the replication job fails)? |
|
Oct 24 |
comment |
How to display differential backup date in SSMS Object Explorer Details There is no way to do this that I am aware of. I use PowerShell to get this information. |
|
Oct 24 |
comment |
Post replication powershell script - on subscriber This is snapshot replication I take it? If that's the case then why not schedule a step after replication that uses SQLCMD or Invoke-SQLCmd to run exec sp_start_job on the remote server? |
|
Oct 24 |
comment |
tempdb thrashing and mirroring permissions (SQL Server) There should not be any relationship between the two, but it's worth eliminating that error anyway. Is mirroring meant to be setup between two servers? If not, disable the mirroring attempt on the remote server. If so then grant connection on that tcp endpoint to the login. |
|
Oct 15 |
comment |
Multi-Table Join to Single Destination Just out of curiosity, did you appropriately index the columns on the destination and source tables for the second version that you are attempting to run? That could easily make up the huge time difference. |
|
Sep 21 |
comment |
When restoring a SQL Server DB from dump files on a remote NAS share, copy before restore or restore directly? Network stability and speed truly are the differentiators here. I backup all of my databases across the network, but those are all on 10Gb pipes. You might consider copying the file across if you are using a slower network as there are copy optimizations done with threading in Robocpoy. As always your mileage may vary, so I would recommend testing with various sizes of databases. |