Search Results

Honestly with a 32 Gig database physical fragmentation shouldn't be much of an issue unless you don't have a couple of gigs of RAM.

Why would you build a table to log the emails into, then have another process come through and read the emails from the table in order to send them via database mail. Why not just modify your applica …

You need to either have a SAN admin look at the system of bring a consultant in to look at it. (Yes I'm a SAN consultant, no that's not why I'm saying this.)

For a 64bit build of SQL to use the Access drive you'll need to install the 64bit version of the Access drive. If you have the 32bit version of Office installed you'll need to either remove that and …

Why are you specifying "Initial Catalog=mydb;database=mydb;"? You should be using one or the other, not both. Your connection string should look like this. Provider=SQLOLEDB;Data Source=MYPC\MSSQLS …

Security isn't part of SQL Replication. That has to be done manually.

If you change the recovery model to SIMPLE to back to either FULL or BULK_RECOVERY you make all your transaction log backups useless. The recovery model shouldn't every be changed regularly. Shrinki …

You'll need to completely uninstall the SQL 2008 R2 tools, then reinstall them from the SQL 2008 R2 Enterprise Edition media.

If sounds to me like your statistics are becoming stale which is causing the SQL Server to use a crappy execution plan to get to the data. Can you post the execution plan for when the query is workin …

You'll want this. CREATE VIEW VIEW2 AS SELECT [Column1], cast(NULL as varchar(10)) AS column2 FROM VIEW1;

Stop using the function, it is killing your performance. Scalar functions are executed once for each row, so you have to scan the entire table in your example, then as you are scanning the table exec …

Run DBCC CHECKDB without the repair option. What does it tell you? If the system tables are corrupt then it's game over and time to restore from backup.

Log shipping to the primary site then doing backups isn't going to work as you can't backup a database which is waiting for t-log backups. With SQL 2008 your only option would be to backup to local d …

Google for sp_help_revlogin and find the version for your version of SQL (the SQL 2008 version works on SQL 2008 and up). Install this sp on the old server. Run sp_help_revlogin on the old server. …

sp_dropserver and sp_addserver are only used to tell the SQL Instance that the name of the physical computer has been changed. There is no way to change the name of the instance without reinstalling …