RBarryYoung (3/26/2010)

---

Trey Staker (3/26/2010)

---

Kit G (3/26/2010)

---

[... I also didn't realy understand what she was trying to get across and she didn't take the time to clarify her prior posts, just...

To SwePeso:

Show off :w00t:

I like it - nice solution.

Absolutely - the DMV's open up a lot of good information and make Performance Dashboard a real useful tool 😉

Michael Meierruth (3/26/2010)

---

Oops, it appears I misused the term "don't ask questions". Note, I have changed it to lower case. This should help in calming down everyone.

I was simply trying...

Michael Meierruth (3/26/2010)

---

DakotaPaul,

The WITH statement is the best thing that came out with SS2005.

And there is no need to wrap your head around it. It's really simple!

It's like preparing your...

Backup history is stored in the system tables in MSDB. Look in the backup* tables in that database to find the information you are looking for.

You need to look in the setup logs and post the errors here - looking at what you posted doesn't tell us what errors were encountered.

The setup logs are going...

I don't know if there are any documents available for that - but I can tell you that best practices are to never open up databases to public roles.

The application...

Yes - you do not need SSIS installed to create or run maintenance plans in SQL Server 2005. As long as you are at SP1 or greater (I think...

I don't know what is so hard about it - right click on the table in the other database and script it to a select statement. Find the timestamp...

I am thinking something like this might be what you are looking for:

;With cteGrouped (MarkPer, StartDate, EndDate, RowNum)

As (

Select MarkPer

,StartDate

...

Yes, there is an easy way to do this. Rewrite your insert statement to include all of the columns being inserted - without the timestamp column. For example:

Current:

INSERT...

If you upgrade to SQL Server 2008 - you can defragment HEAP tables. Other than that, you need to continue as you are now.

If you are consolidating on a single instance of SQL Server, your only option is going to be scripting out the jobs and rebuilding on the new server.

Why would you want to do this?

There is a public role available - it does not have any permissions by default. You could add permissions to this role, but...