1) centrainly not a good practise to use sysadmin privileges in regular aps.

(even for testing ! The sooner you encouter a security issue the better !!)

2) are you getting an...

Just my 2 ct.

You're still running SQL2008R2 RTM version.

Current is 2008 R2 Service Pack 2 ( and if you also do the CU it is on CU7 for...

does the sqlserver service account of your target server have the needed windows auth to read the backup file at the location you pointed to ?

Ronen Ariely (7/16/2013)

---

Perry Whittle, i will add a comment about this maybe. thanks

But actually as the entire article is not discuss an ideal case, but a case study which should...

Nice article. Thank you for sharing.

I've always used this ref. "Negative Process ID (spid -2) in SQL Server" to guide me through this situation 🙂

jacquereed (7/15/2013)

---

I put down the answer 6,6,8,6 and it said I got it wrong, but when I ran it through my sql server, it put out exactly that -- What's...

This isn't only a great solution for the problem,

it also gets rid of the dynamic sql in the sproc, which is always a horrible thing you should...

Caps off, please. No need to shout. :ermm:

You would have to code 3 inserts

or

( since you are posting in the SQL2008 forum )

You could code a single insert and...

with regards to your Powershell script:

do you actually use an xlsx template to fill out with your data?

do you actually use any excel functionallity at all ?

if not: just change...

let me answer Q1 for you : Yes

ref: Version and Edition Upgrades http://msdn.microsoft.com/en-us/library/ms143393%28v=sql.105%29.aspx

Q3 We prefer upgrading using the migration path (backup/restore).

With inplace upgrades, the instance is configured starting from...

actually ... the correct answer may not be that correct at all :hehe:

It all depends on your ANSI_PADDING setting in use.

set ansi_padding off ;

declare @Vchar varchar(12)='prasad '

...

nice and simple trick.

Thank you for sharing.

have a look at http://msdn.microsoft.com/en-us/library/ms191545%28v=sql.105%29.aspx

it loads the default trace data into a temp table and queries it so it only shows Auto Grow events in a first query en in a second query it...

If you have default traces enabled ( should be the sqlserver default unless your installation dated pre RTM ), you can find information what extended your (temp)db.

/*

* Import Default...